Built for an assistant
- Paper only. Paper orders and paper bots trade at live prices and no money moves.
- Only the tools a key can use. A read key never sees the paper tools, so a model never plans around a call it cannot make.
- Safe retries. A paper order carries a
requestId, so a retry after a timeout returns the first order instead of placing a second. - Errors that say what to do next. Every failure carries a stable
code and a hint. - Answers sized for a model. Lists return 20 rows unless asked for more, and every tool says which one to call next.
Limits
Limits are per account and shared with the REST API: 120 requests a minute, 5,000 trades older than an hour and 100 different traders a day. Each extra section of a market or trader and each extra backtest scan counts as one more request. See the rate limits and errors pages, and the developer docs for every route with samples in curl, Python and TypeScript.
Frequently asked questions
What is a prediction market MCP server?
An MCP (Model Context Protocol) server gives an AI assistant tools it can call. Rivo's server gives Claude, ChatGPT, Cursor or any MCP client the whale trades, trader records, market data and backtester behind Rivo, so you can ask it what the money is doing on Kalshi and Polymarket and have it check an idea against settled markets.
Is it local or remote?
Remote, over HTTP. There is nothing to install or run. Add the endpoint to your client with your API key as a bearer header and the tools appear.
Which clients work?
Anything that speaks MCP over HTTP with custom headers: Claude Code, Claude Desktop and claude.ai connectors, Cursor, ChatGPT connectors, and agents built on the MCP SDKs. The docs carry the exact setup for each.
Can an AI spend my money through this?
No. The server trades on paper only: paper orders and paper bots run at live prices and no money moves. A read key cannot even see the paper tools; a key with write access can place paper orders and start paper bots.
What does it cost?
It is included in the Rivo subscription, $9 a week or $15 a month. Just one trade can pay for it. The limits are per account and shared with the REST API: 120 requests a minute, 5,000 trades older than an hour and 100 traders a day.
How is a backtest's return worked out?
The way prediction market contracts settle: a winning contract pays $1 and a losing one pays nothing. A $100 stake at 20 cents makes $400 profit on a win and loses $100 on a loss. Stakes default to a flat $100 a trade so two ideas compare fairly. The methodology page has every formula.
Is there a plain REST API too?
Yes. Every tool returns the same data as a v2 API route, with the same keys and limits. Use the API when you want to script it yourself and MCP when you want an assistant to drive.