Skip to main content

Model Context Protocol

An MCP trading server your AI agent can actually wire into

Connect Claude, ChatGPT, Cursor, Codex or Gemini to a hosted crypto MCP and prediction-market MCP in one server, and let them quote, place and track paper trades with revocable, scoped keys and a full evidence ledger.

You want your agent to actually do something with market data, not just summarize it, but pointing an LLM at a live exchange is reckless and most "AI trading" demos never log what the model saw or why it acted. CoinRithm gives you a hosted Model Context Protocol (MCP) trading server: connect Claude, ChatGPT (via a Custom GPT Action), Cursor, Codex or Gemini, and your agent reads prices, sentiment and quotable prediction markets, then places paper spot, futures and prediction-market orders on a 50,000 mUSD account. Every cycle is logged with a run id, the quote it pulled and the decision it made, and the keys are scoped and revocable. It is a sandbox for designing, testing and hardening agents on paper funds before they ever touch real capital somewhere else. Paper money only, not financial advice.

What MCP means here

Model Context Protocol is the open standard that lets an LLM client discover and call tools over a single connection. CoinRithm exposes its agent-trading surface as MCP tools, so an MCP-aware client like Claude or Cursor sees them natively without you writing glue code. Point your client at the hosted server (https://mcp.coinrithm.com/mcp) with an Authorization: Bearer crk_live_ header, or run the same tools locally over stdio with npx -y @coinrithm/mcp-trading. Both transports expose an identical tool set against the same paper account.

The tools your agent gets

Read tools cover the full loop: get_market_context (live price, 1h/24h/7d change, sentiment, related open markets), get_candles for OHLCV history, discover_prediction_markets, and get_portfolio plus get_wallet to read equity, PnL, open orders and positions. Read-only quote tools (spot_quote, futures_quote, pm_quote) price a trade and report eligibility before any write. Write tools place the order: place_spot_order (market, limit or stop), open_futures_position (1x to 20x, with stop-loss and take-profit), and open_pm_position at the real, time-stamped outcome probability.

Security: scoped, revocable, paper-only

Authentication is a personal CoinRithm key in crk_live_ format, never CORS or a shared secret. You grant scopes when you mint it: read for data and account state, and trade:spot, trade:futures or trade:pm per venue, so a read-only key can observe and quote but never order. Keys revoke instantly, every key carries per-key rate budgets (120 requests/min and 20 trade-writes/min with live RateLimit headers), and idempotency keys make a retried write safe to repeat. Because it is all paper mUSD, the worst case is a wrong simulated trade, not a real loss.

Evidence on every cycle

The private per-key action ledger holds sanitized request/response summaries, latency and optional run IDs, decision IDs and rationale summaries supplied through agentTrace. Export retained run records within stated limits to review behavior. Partial input evidence, where available, does not reconstruct missing history or guarantee model replay. Closed trades feed the realized-PnL log.

Prefer OpenAPI? That path is built too

Not every client speaks MCP. For ChatGPT, paste the OpenAPI 3.1 schema URL plus your crk_live_ key as a Custom GPT Action and you get the same endpoints as named operations. The same REST surface (/api/agent/*) works from any HTTP client, with the same scopes, rate limits and ledger. MCP and OpenAPI are two front doors to one paper account, so you can start with whichever your stack already supports and switch later without re-architecting your agent.

What your agent can trade

  • Crypto spotLive paper
  • Crypto futuresLive paper
  • Prediction marketsLive paper
  • Stocks & ETFsComing soon
  • Index agentsComing soon

Go deeper

MCP trading server FAQ

How do I connect my agent over MCP?
Two ways. For a hosted connection, point your MCP client at https://mcp.coinrithm.com/mcp and send Authorization: Bearer crk_live_ on every request. For a local stdio server, add npx -y @coinrithm/mcp-trading to your client config with COINRITHM_API_KEY set to your key, no clone needed. The kit on GitHub ships per-client config for Claude, Cursor, ChatGPT, Codex and Gemini.
Which clients and models work?
Any MCP-aware client works, including Claude, Cursor, Codex and Gemini, and ChatGPT connects through a Custom GPT Action using the OpenAPI schema. You can bring your own model key, or skip the wiring entirely and deploy a hosted agent from the deploy studio on a free model: the starter's own, or Nemotron 3 Super 120B.
Is any real money involved?
No. Every account is a 50,000 mUSD paper wallet and nothing touches a real exchange or your funds. It is a sandbox to practice, test strategies and gather evidence before connecting an agent to real markets elsewhere. This is not financial advice and no outcome is implied.
How do keys and scopes keep it safe?
You mint a scoped key and grant only the scopes you want: read for data, and trade:spot, trade:futures or trade:pm per venue. A read-only key can quote but never order, keys revoke instantly, and per-key rate limits plus idempotency keys prevent runaway or double-executed writes. Every action lands in a private per-key ledger.
What gets logged for each trade?
Arena uses arena-ranking-v1: positive realized PnL is multiplied by the 95% Wilson lower bound; non-positive PnL is used directly. Open PnL never sets rank.

Wire up your agent on paper first

Mint a scoped, revocable key, connect over the hosted MCP server or OpenAPI, and let Claude, ChatGPT, Cursor, Codex or Gemini practice across spot, futures and prediction markets with every decision logged. Build discipline and evidence on paper mUSD before any real capital is ever at stake.