Sato Hub
Trading Tool

Simmer

Prediction-market harness for agents: one SDK, MCP server and skill catalogue to trade Polymarket and Kalshi, with a virtual $SIM practice venue.

  • Sato Score68
  • ChainsPolygon
ActiveSelf-ReportedActive · 1d ago

Simmer is a partly open-source trading tool on Polygon, with last code activity on 2026-11-06 (Active). Latest release on 2026-06-10. Sato Score 68/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-07. How the score works →

Check what an install would ask of your keys, before you run it →

Last commit Nov 6, 2026 · Last release Jun 10, 2026 · ★ 52

Listed from simmer.markets on 2026-09-23. Install: not attempted — no install path on record. Evidence →

Next step

Watch Simmer

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on spartanlabsxyz/simmer-sdk before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Simmer calls itself "where agents trade prediction markets". It offers a Python SDK, an MCP server (npx simmer-mcp, no key needed to browse), and installable trading skills for Polymarket and Kalshi (simmer.markets/llms.txt). Per its skill.md, trades default to a virtual $SIM venue, and real-money trading must be opted into explicitly, with safety rails and self-custody wallet options. Developers can publish their own strategies to the skills catalogue. The SDK repo is MIT-licensed.

Sato Score

68/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
14/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
10/15
Independent verification
3/10

Evidence — listed vs checked · what the words mean

Listed from simmer.markets on 2026-09-23. Install: not attempted — no install path on record.

ClaimValueEvidenceSourceChecked
Chains supportedPolygonself-reporteddocs.simmer.marketsas of 2026-11-07
Verification statusSelf-Reported — not independently reviewedself-reportedsimmer.marketsas of 2026-11-07
Recent activitylast release 2026-06-10 · last commit 2026-11-06observedgithub.com/SpartanLabsXyz/simmer-sdk2026-11-07
Website answersanswered (HTTP 307)observedsimmer.markets2026-11-07
Daily check record45 of 45 daily checks since 2026-09-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-11-06
Works withOpenClaw, ClawHub, MCP, Polymarket, Kalshi, Hyperliquid, PyPI, npmconfidence 0.80self-reportedgithub.com/SpartanLabsXyz/simmer-sdkas of 2026-10-01
Tagsprediction-markets, polymarket, kalshi, mcp, agent-skills, sdk, hyperliquid, op…confidence 0.80self-reportedgithub.com/SpartanLabsXyz/simmer-sdkas of 2026-10-01
Sato Score68/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-11-07

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Observed record — 46 daily checks since 2026-09-23

100%of 46 checks since 2026-09-23 succeeded
Currently responding for 46 days
Succeeded
46
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.

Last 30 days — to 2026-11-07, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
68
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Polygon
Agent types
Trading, Skill
Open source
Partial
Works with
OpenClaw, ClawHub, MCP, Polymarket, Kalshi, Hyperliquid, PyPI, npm
Last checked
2026-11-07

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#prediction-markets#polymarket#kalshi#mcp#agent-skills#sdk#hyperliquid#openclaw#paper-trading#backtesting#self-custody
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Simmer's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 1, 2026
    Auto-enriched: supported integrations, tags
  2. Sep 23, 2026
    Listed on Sato Hub
  3. Sep 23, 2026
    Sato Hub began tracking this listing

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Simmer

Is Simmer open source?
Partly. Some of Simmer is published as source (https://github.com/SpartanLabsXyz/simmer-sdk) and some is not. Checked as of 2026-11-07.
Which chains does Simmer support?
Simmer lists support for Polygon as of 2026-11-07.
Is Simmer still maintained?
The most recent code activity Sato Hub observed was on 2026-11-06 (last commit 2026-11-06, last release 2026-06-10), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Simmer?
Sato Hub has no deploy spec for Simmer; follow the project's own documentation at https://docs.simmer.markets.
Is Simmer verified on Sato Hub?
No independent verification is on record for Simmer; its verification status is "Self-Reported" and its Sato Score is 68 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Simmer — Sato Hub." Sato Hub, updated 2026-11-07, accessed 2026-11-07. https://satohub.ai/resources/simmer

Data last refreshed 2026-11-07; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.