Crypto MCP server for AI agents

MarketTrace runs a free, read-only MCP server for crypto perpetual futures. Its ten tools return funding rates with their percentile against up to two years of history, open interest, volume, CVD, order-book imbalance, liquidations and basis, plus candles with delta, volume-profile levels, large trades and footprint events. It covers BTC, ETH, SOL, BNB, XRP, DOGE, HYPE, ZEC and ENA on Binance, Bybit, OKX and Hyperliquid; liquidations come from the first three.

Facts and normalization, no verdicts. Each metric comes with its coverage (the venues that fed it and the history behind it), and every response states its age. An agent can tell a solid number from a thin one before it repeats either.

Server URL

https://api.markettrace.ai/mcp

Copy

Transport

Streamable HTTP

Sign-in

OAuth with an email link. No API key, no card.

Access

Read-only. Every tool is marked readOnlyHint.

Assets

BTC, ETH, SOL, BNB, XRP, DOGE, HYPE, ZEC, ENA

Venues

Binance, Bybit, OKX, Hyperliquid (liquidations: Binance, Bybit, OKX)

Version

1.9.0, released 2026-10-06 · changelog

Registry name

ai.markettrace/agent-feed

Tool contract

tools.json on GitHub, input schemas for all 10 tools

Price

Free

Connect the MCP server

Every client uses the same URL and the same sign-in. The client opens a browser, you type your email, and we send a sign-in link. Open it on the same device and in the same browser where you started, or sign-in will not finish.

Claude (web and desktop)

1. In Claude: Settings → Connectors → Add custom connector.
2. Paste the server URL: https://api.markettrace.ai/mcp
3. Authorize when prompted and open the emailed link.
4. Ask away. The feed is read-only; it can never trade or move funds.

Claude Code and Codex connect from the terminal in two steps. Adding the server does not sign you in, so run both.

Cursor

Use the Add to Cursor button, or add the server to ~/.cursor/mcp.json and sign in when Cursor asks.

Add to Cursor

{
  "mcpServers": {
    "markettrace": {
      "url": "https://api.markettrace.ai/mcp"
    }
  }
}

Other clients and your own agent

Stdio-only clients connect through the standard mcp-remote bridge, which also runs the sign-in:

{
  "mcpServers": {
    "markettrace": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.markettrace.ai/mcp"
      ]
    }
  }
}

Your own agent can use any MCP client library with OAuth support; the official TypeScript and Python SDKs include one. An unauthenticated request gets HTTP 401 with a WWW-Authenticate header that points to the server's OAuth metadata, so the client finds the sign-in flow by itself.

Listed in the official MCP registry as ai.markettrace/agent-feed.

Open-source bridge & docs on GitHub

Things to ask

Plain questions work. The arrow shows the tool an agent reaches for.

• What's the market state for BTC? Is positioning stretched? → get_market_state
• SOL funding is above the 90th percentile. What happened over the next 24 and 72 hours the other times it was that high? → get_market_state, get_conditional_outcomes
• How did ETH open interest build over the last three days? → get_state_history
• How much got liquidated on ETH in the last hour, longs or shorts? → get_liquidations_recent
• Is BTC trading inside yesterday's value area? Any naked POCs nearby? → get_volume_profile, get_market_state
• Any market orders over $1M on BTC in the last hour? Which venue took the biggest one? → get_big_trades
• Were bid walls pulled on SOL before the last drop? → get_footprint_events
• Where did aggressive selling stack up on ETH this morning? → get_stacked_imbalances
• Pull BTC 1h candles with delta for the last two days and work out the ATR. → get_ohlcv
• Which venue is leading the HYPE move? Compare CVD, funding and open interest on Binance, Bybit, OKX and Hyperliquid. → get_market_state

MCP tools: funding, open interest, CVD, liquidations, volume profile, footprint

Ten tools, all read-only. Each one takes a symbol: BTC, ETH, SOL, BNB, XRP, DOGE, HYPE, ZEC or ENA, and names like BTCUSDT work too.

Sample response

get_market_state for BTC at 2026-10-06 13:58 UTC, trimmed to the main blocks. A full response also carries per-venue values, order-book depth, the funding calendar and a coverage entry for every block.

{
  "symbol": "BTC",
  "as_of": "2026-10-06T13:58:41Z",
  "age_seconds": 20,
  "price": { "last": 86267.813, "chg_1h_pct": 0.09, "chg_24h_pct": -0.2, "atr_1h_pct": 0.36, "rv_24h_pct": 32.7 },
  "funding": { "rate_bps": 0.28, "percentile": 26, "streak_h": 680 },
  "oi": { "usd": 19175427019, "chg_1h_pct": 0.14, "rel": { "1d": 1.0195, "1w": 1.0345, "1m": 1.059 } },
  "volume": { "usd_24h": 22309245455, "rel": { "1d": 1.3568, "1w": 1.416, "1m": 1.2496 } },
  "cvd": { "window": "30m", "delta_usd": 121145644, "taker_buy_ratio": 0.5558 },
  "obi": { "skew": -0.0097 },
  "liq": { "usd_1h": 1276732, "long_ratio": 0.0614, "percentile": { "1w": 80, "1m": 87 } },
  "basis_bps": -6.33,
  "drivers": [
    "funding 26th pct (730d, binance+bybit+hyperliquid)",
    "OI 1.1x monthly median",
    "volume 1.4x weekly median",
    "liq 80th pct (1w), 6% longs",
    "OI +0.1%/1h, price +0.1% — new longs"
  ],
  "coverage": {
    "funding": { "venues": ["binance", "bybit", "hyperliquid"], "window_days": 730, "n_samples": 2190, "partial": false },
    "liq": { "venues": ["binance", "bybit", "okx"], "partial": false },
    "basis": { "venues": ["binance"], "partial": true }
  },
  "stale_venues": [],
  "feed": { "version": "1.9.0", "tools": 10 }
}

Coverage: assets, venues and history

The cross-venue funding rate and its percentile use venues with at least 365 days of funding history; responses list them in the funding coverage entry. Basis compares the Binance perp with a multi-exchange spot index. Hyperliquid has no liquidation feed.

• Assets: BTC · ETH · SOL · BNB · XRP · DOGE · HYPE · ZEC · ENA.
• Funding percentile: up to 730 days of history.
• Trade tape (candles, big trades, stacked imbalances, volume profile): 31 days; 14 for ZEC and ENA.
• State archive (get_state_history and archived conditions): a row every 15 minutes since 2026-07-03.
• Wall events: since 2026-10-03.
• Live blocks refresh about every 30 seconds.

Rules for agents reading this feed

These eight rules keep an agent from misreading the numbers. They also work as a system prompt.

1. Call get_market_state first. One call covers funding, open interest, volume, CVD, the order book, liquidations, basis and drivers for one asset.
2. Read the coverage entry before quoting a number. partial: true means the block rests on fewer venues or less history than the full set; reason, when present, says why: accruing, unavailable, degraded or stale. Basis is always partial because it uses Binance only.
3. Check stale_venues and age_seconds. age_seconds is the age of the oldest live source behind the response.
4. Mind the scales. Percentiles run 0 to 100, fields ending in _ratio run 0 to 1, rel values are multiples of the trailing median (1.4 means 140%), obi.skew runs from −1 to +1 and is positive when bids are heavier, and basis_bps is positive when the perp trades above spot.
5. In get_ohlcv, v and delta are in base units, not USD. Leave a partial candle out of ATR and volatility math.
6. Treat liquidation USD as an estimate, and remember that Hyperliquid is not in it.
7. When get_conditional_outcomes returns history_silent, say the history is too thin to measure. Do not fill the gap with a guess.
8. Report the numbers as measurements. The feed says what happened, not what to trade.

Limits and errors

Limits apply per account.

• Tool calls: bursts of up to 60, then one every 2 seconds (30 a minute).
• The heavier tools, get_ohlcv, get_state_history, get_big_trades and get_stacked_imbalances, also share a tighter budget: bursts of up to 20, then one every 6 seconds (10 a minute).
• All requests together: bursts of up to 200, then 10 a second.
• A throttled tool call comes back as a tool error the model can read, for example "Rate limit (call): retry after 2 s". Past the request budget the server answers HTTP 429 with a Retry-After header.
• Parameters outside a tool's range return an error and are never trimmed to fit: windows over 24 h in get_liquidations_recent and get_footprint_events, over 12 h in get_big_trades and get_stacked_imbalances, and candles beyond the 31-day tape in get_ohlcv.

Honesty model

The feed reports what it can measure and says so when it can't: thin history answers with disclosed depth instead of made-up numbers, conditional outcomes go history_silent below the evidence floor, and every response self-declares freshness. Reports history, not predictions.

Free and open source

The hosted MCP server is free: no API keys, no card, OAuth via email magic link. The stdio bridge, connection configs and the full tool contract are open source (MIT) on GitHub. The feed is read-only by design: it can never trade or move funds.

FAQ

Related

• MCP methodology: how the feed computes each number
• What MCP is
• Crypto MCP servers compared
• Funding-rate extremes, measured with get_conditional_outcomes
• What an MCP server is, explained for traders
• Documentation

Privacy Policy · Terms of Service