Getting started
MCP server
A remote MCP server over HTTP. Nothing to install and nothing to run: point your client at the endpoint, pass your key as a bearer header, and the tools appear.
https://api.rivo.markets/mcpClaude Desktop, Cursor and JSON-config clients
Most clients take the standard mcpServers JSON. Claude Desktop reads it from its MCP settings; Cursor from ~/.cursor/mcp.json.
{
"mcpServers": {
"rivo": {
"url": "https://api.rivo.markets/mcp",
"headers": { "Authorization": "Bearer rivo_live_..." }
}
}
}Claude Code
claude mcp add rivo https://api.rivo.markets/mcp \
--transport http \
--header "Authorization: Bearer rivo_live_..."How it behaves
- Auth is per request with the same keys as the REST API; see Authentication.
- The rate limit is shared with REST. Tool fan-out (sweep, compare) is charged per variant on both sides.
- Tools only ever touch the account behind the key. Strategies cannot be edited or deleted through the server, so a confused agent cannot destroy a history you built.
Tools
Ten tools, each backed by the same handler as its REST endpoint. The endpoint pages carry the full parameter and response reference; the notes here are what differs when calling through MCP.
What data exists to test against: categories and their trade counts, date coverage, settled counts, and the price and size distributions.
Call this first. Writing a rule without it usually produces criteria that match nothing.
Score a rule against markets that already resolved. Saves nothing, so it is safe to call repeatedly while exploring.
Set holdout: true to score the earlier period and validate on the later one. Use it before recommending a rule.
Score one rule across a range of values for a single numeric field, in one call.
Charged per value against the rate limit: a sweep across five values costs five requests.
Score several unrelated rules side by side in one call, each with a label.
Charged per variant against the rate limit.
Split one rule's results by category, platform, month or price band, to see where it works and where it does not.
Find recently active markets by name, with the whale trades behind each.
The individual trades a rule matches, for inspecting specifics rather than aggregates.
Prefer backtest when you want a score; this returns rows and is slower.
Turn a rule into a live strategy on the account. It keeps claiming matching trades as they happen and alerts you.
Create-only: strategies cannot be edited or deleted through the API, so a confused agent cannot destroy a history you built.
The account's strategies with their current record.
Full performance for one saved strategy: settled record, realized and open PnL, and the return curve.
Returns the rollup, event count and curve only. The full event list is large and rarely what a model needs; use the REST endpoint for rows.