原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Simmer

作者:SpartanLabsXyz版本 3.3.2i★ –i在你的电脑上运行
注册名称io.github.adlai88/simmer-mcp

安装

概览

作者提供的说明(英文原文)

Trade prediction markets with AI agents — skill discovery, autoresearch, and execution.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他
  • 你需要填写:SIMMER_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 0 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: SIMMER_API_KEY, SIMMER_MCP_ALLOW_LIVE

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "simmer": {
      "command": "npx",
      "args": [
        "-y",
        "simmer-mcp"
      ],
      "env": {
        "SIMMER_API_KEY": "your-value",
        "SIMMER_MCP_ALLOW_LIVE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add simmer --env SIMMER_API_KEY=your-value --env SIMMER_MCP_ALLOW_LIVE=your-value -- npx -y simmer-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "simmer": {
      "command": "npx",
      "args": [
        "-y",
        "simmer-mcp"
      ],
      "env": {
        "SIMMER_API_KEY": "your-value",
        "SIMMER_MCP_ALLOW_LIVE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "simmer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "simmer-mcp"
      ],
      "env": {
        "SIMMER_API_KEY": "your-value",
        "SIMMER_MCP_ALLOW_LIVE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • SIMMER_API_KEY 机密 env
    Simmer API key (sk_live_...) from simmer.markets/dashboard. Required for Pro tools (autoresearch, trading, briefings). Free tools work without it.
  • SIMMER_MCP_ALLOW_LIVE env
    Set to 'true' to allow live trading via simmer_trade. Without this, all trades run in paper/sim mode.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ! 注意

    作者与仓库一致

    发布者(adlai88)不是仓库所有者(SpartanLabsXyz);可能是其他人代为上架的

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18623 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18623 个服务器的 8% 更新
  • 基础检查结果等于或优于此分类中其他 18623 个服务器的 16%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Simmer 安全吗?

它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:SIMMER_API_KEY

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(3.3.2)于6个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, NexusWindows

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者:formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者:desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

NexusWindows

Windows computer use in the background: desktop apps driven without your mouse or keyboard.

作者:pironjulien非常新今天更新

在你的电脑上运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Simmer SDK

Simmer is the leading prediction market harness for AI agents. Autonomous agents place trades on venues like Polymarket, Kalshi and Hyperliquid through a unified API — with self-custody wallets, safety rails, and smart context.

  • Prediction market harness for AI agents — designed for autonomous agents, with full support for manual trading too. Users install trading skills and let their agents trade autonomously.
  • $SIM simulated trading — paper-trade with virtual currency before risking real funds.
  • Multi-venue — trade Polymarket, Kalshi and Hyperliquid through one unified API.

What's in this repo

skills/28 skills an agent installs and runs. skills/simmer/SKILL.md is the canonical source for simmer.markets/skill.md.
mcp/MCP server, published to npm as simmer-mcp.
simmer_sdk/Python SDK, published to PyPI as simmer-sdk.

Installation

pip install simmer-sdk

Get your API key from simmer.markets/dashboard.

Quick Start

OpenClaw Skill Pattern (recommended)

Most Simmer users run trading skills inside OpenClaw. The standard pattern uses a lazy singleton client and reads config from environment variables:

import os

from simmer_sdk import SimmerClient

SKILL_SLUG = "my-skill-slug" # Must match your ClawHub slug TRADE_SOURCE = f"sdk:{SKILL_SLUG}"

_client = None def get_client(live: bool = False): global _client if _client is None: venue = os.environ.get("TRADING_VENUE", "sim")

live controls paper vs real execution and is a constructor arg, not a

per-trade flag. live=False => paper preview (no real order placed).

_client = SimmerClient(api_key=os.environ["SIMMER_API_KEY"], venue=venue, live=live) return _client

def run(live: bool = False): client = get_client(live)

Find markets. Unfiltered browse is windowed to the newest ~1,000 active

markets — filter with sort="volume", q="...", or tags="..." to reach the rest.

markets = client.get_markets(status="active", sort="volume", limit=20)

Get trading context (safeguards, slippage, conflict detection)

ctx = client.get_market_context(markets[0].id)

Trade — always tag source and skill_slug

if not ctx.conflict and ctx.recommended_action != "hold": result = client.trade( market_id=markets[0].id, side="yes", amount=10.0, source=TRADE_SOURCE, skill_slug=SKILL_SLUG, reasoning="Signal detected — buying YES" ) print(f"{'PAPER: ' if not live else ''}Bought {result.shares_bought:.2f} shares")

if name == "main": import sys run(live="--live" in sys.argv)

Set environment variables:

export SIMMER_API_KEY=sk_live_...

export TRADING_VENUE=sim # sim | polymarket | kalshi export WALLET_PRIVATE_KEY=0x... # Required for Polymarket self-custody

Default to dry-run. Skills should require --live to execute real trades. Paper-trade with $SIM until your edge is consistent, then graduate to real money.

Raw SDK

For developers building custom integrations:

from simmer_sdk import SimmerClient

client = SimmerClient(api_key="sk_live_...")

Browse markets (unfiltered browse is windowed to the newest ~1,000 active

markets — use sort="volume", q="...", or tags="..." for discovery)

markets = client.get_markets(sort="volume", limit=10) for m in markets: print(f"{m.question}: {m.current_probability:.1%}")

Trade with $SIM (virtual currency)

result = client.trade(market_id=markets[0].id, side="yes", amount=10.0) print(f"Bought {result.shares_bought:.2f} shares for ${result.cost:.2f}")

Check P&L

for p in client.get_positions(): print(f"{p.question[:50]}: P&L ${p.pnl:.2f}")

Trading Venues

VenueCurrencyDescription
sim$SIM (virtual)Default. Paper trading on Simmer's LMSR markets.
polymarketUSDC.e (real)Real trades on Polymarket (Polygon). Requires WALLET_PRIVATE_KEY.
kalshiUSDC (real)Real trades on Kalshi. Requires Pro plan.
# Paper trading (default)

client = SimmerClient(api_key="sk_live_...", venue="sim")

Real trading on Polymarket

client = SimmerClient(api_key="sk_live_...", venue="polymarket", live=True)

Read-only validation/status client. Does not process constructor-time risk exits.

client = SimmerClient.readonly(api_key="sk_live_...", venue="polymarket")

Override venue for a single trade

client.trade(market_id, side="yes", amount=10.0, venue="polymarket")

TRADING_VENUE environment variable is read at client init — OpenClaw skills use this to select venue at startup without code changes.

Constructor side effect: for live Polymarket clients with WALLET_PRIVATE_KEY or OWS_WALLET, regular SimmerClient(...) construction checks pending risk alerts and may submit stop-loss/take-profit exit orders. This is intentional for self-custody safety: Simmer's server cannot sign those exits. Pass process_risk_alerts=False to skip this constructor check for dry runs. Use SimmerClient.readonly(...) for API-key validation, preflight/status checks, and other non-trading paths.

Spread caveat: $SIM fills instantly (AMM, no spread). Real venues have orderbook spreads of 2–5%. Target edges >5% in $SIM before graduating to real money.

Polymarket order types: omit order_type for the SDK/server smart default: buys use FAK (fill what is available immediately), sells use GTC (rest on the book to improve fill rate on thin books). For structurally thin markets or maker-style limit entries, pass order_type="GTC" and an explicit price.

Polymarket Protocol V2 orders

Protocol V2 markets use PositionManager positions and the ExchangeV3 signing domain, version "3". This is separate from the April V2 order format selected by SIMMER_POLYMARKET_EXCHANGE_VERSION. Raw-key EOA signing and both raw-key and OWS deposit-wallet signing support these markets. OWS EOA signing remains legacy-only and rejects Protocol V2 metadata.

trade() reads the selected outcome's protocol from the Simmer market detail response. The server must return these fields on market detail and discovery responses before routing Protocol V2 markets through this SDK:

FieldCurrent marketsProtocol V2 markets
polymarket_protocol_versionAbsent or "v1""v2"
polymarket_position_idAbsent or nullYES position ID as a decimal uint256 string
polymarket_no_position_idAbsent or nullNO position ID as a decimal uint256 string
polymarket_neg_riskExisting booleantrue for the neg-risk module, false for binary

For current markets, polymarket_token_id and polymarket_no_token_id remain the signing IDs. For Protocol V2, the position ID becomes the signed tokenId; legacy token IDs are not required. The server must obtain the protocol and IDs from authoritative market metadata. The SDK does not infer them from dates, IDs, or the neg-risk flag. Unknown or null protocol markers and incomplete V2 metadata raise ValueError. The SDK caches market detail for the client session.

Market.polymarket_yes_protocol and Market.polymarket_no_protocol expose validated MarketProtocol values. Direct signing callers can pass market_protocol=MarketProtocol("v2", position_id) to build_and_sign_order, importing MarketProtocol from simmer_sdk.polymarket_contracts. The frozen value requires a position ID for V2 and forbids one for V1. Both signing paths consume the same value. build_and_sign_order rejects Protocol V2 with the legacy exchange flag.

client.ensure_approvals(protocol_v2=True) checks the existing approvals plus pUSD allowance and PositionManager operator approval for ExchangeV3. client.check_approvals(protocol_v2=True) requests GET /api/polymarket/allowances/{address}?protocol_v2=1. The server must return boolean entries in allowances named pusd_ and position_manager_ , using the full lowercase ExchangeV3 address:

  • pusd_0xe3333700ca9d93003f00f0f71f8515005f6c00aa is true when pUSD allowance(owner, ExchangeV3) >= (2**256 - 1) // 2, PolyNode's readiness threshold.
  • position_manager_0xe3333700ca9d93003f00f0f71f8515005f6c00aa is the result of PositionManager isApprovedForAll(owner, ExchangeV3).

Missing entries mean unapproved, even if an older server reports all_set=true.

With protocol_v2=True and a locally configured wallet, default-address check_approvals(), ensure_approvals(), and set_approvals() require activation status from GET /api/sdk/agents/me:

  • If per_agent_wallet_address is present, per_agent_dw_active must be a boolean. When true, approval checks use per_agent_deposit_wallet_address.
  • Otherwise, wallet_uses_deposit_wallet must be a boolean. When true, approval checks use deposit_wallet_address.

When the applicable flag is false, approval checks use the configured EOA address. These calls fail closed: missing, null, or non-boolean activation status raises, and identity lookup errors propagate. An active DW without its address also causes approval checks to raise. Passing an explicit address to check_approvals() skips activation discovery and checks that address directly, including with protocol_v2=True.

For an EOA, client.set_approvals(protocol_v2=True) can submit the missing approvals. Deposit-wallet users must use the dashboard's Activate Trading flow, whose server implementation must also grant both approvals from the deposit wallet. The SDK does not submit EOA approvals for a deposit wallet. The default approval methods retain their existing scope. Managed wallets without a local address cannot confirm Protocol V2 readiness through this SDK.

Paper trading on real venues

Pass live=False to simulate trades with real market prices — no wallet or USDC required. For Polymarket, fills model the CLOB bid-ask spread for realistic P&L. Resolved markets auto-settle (winning shares pay $1, losers $0).

client = SimmerClient(

api_key="sk_live_...", venue="polymarket", live=False, # Simulate fills, no real money starting_balance=10_000.0 # Virtual capital (default: 10,000) )

result = client.trade(market_id=markets[0].id, side="yes", amount=50.0, reasoning="Testing strategy") print(f"Filled {result.shares_bought:.2f} shares (simulated)")

Portfolio summary

summary = client.get_paper_summary() print(f"Balance: ${summary['balance']:.2f}, P&L: ${summary['total_pnl']:.2f}")

Graduation path: sim (instant fills, no spread) → polymarket + live=False (real prices, spread modeled) → polymarket live (real USDC).

Backtesting

The three modes above are all *live-forward*. To test a strategy on historical data before risking capital, backtest the skill bundle:

pip install 'simmer-sdk[backtest]'

Try it offline — bundled 10-market demo slice, no data download:

simmer backtest --demo

Backtest your own skill over a window — the tape is fetched + cached for you:

simmer backtest ./my-skill --entrypoint run.py \ --t0 2026-03-01 --t1 2026-03-08 --cadence 12h --out report.json

...or by duration, and with your own local slice (BYO):

simmer backtest ./my-skill --entrypoint run.py --window 30d simmer backtest ./my-skill --entrypoint run.py --tape ./slice --t0 2026-03-01 --t1 2026-03-08

Narrow the fetched slice to a topic — matches question OR slug, applied

before the volume cap, so a niche topic isn't cr

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx