MCP Server

The remote server speaks streamable HTTP at https://cryptodataapi.com/mcp and authenticates with an X-API-Key: cdk_live_YOUR_KEY header. This is the recommended path — no Node, no package, and every tool call runs against our live stack (auth, tier gating, caching and rate limits all included).

Most clients take a one-line add command. Here it is for Claude Code; the exact form for each client is on its own page: Claude Code, Claude Desktop, Claude (web), Cursor, OpenAI Codex, Gemini CLI, Windsurf and GitHub Copilot.

claude mcp add --transport http cryptodataapi \
  https://cryptodataapi.com/mcp \
  --header "X-API-Key: cdk_live_YOUR_KEY"

{
  "mcpServers": {
    "cryptodataapi": {
      "url": "https://cryptodataapi.com/mcp",
      "headers": { "X-API-Key": "cdk_live_YOUR_KEY" }
    }
  }
}

If your client only supports stdio MCP servers, install the published cryptodataapi-mcp npm package. It is a thin bridge that forwards to the same hosted server — all tool logic still runs server-side, so you get identical behavior. It needs Node.js and reads your key from the CRYPTODATA_API_KEY environment variable.

Add it via CLI, or drop the block below into your client's config file (Claude Desktop, Cursor, Windsurf, and others use this exact mcpServers shape).

CRYPTODATA_API_KEY=cdk_live_YOUR_KEY \
  claude mcp add cryptodataapi -- npx -y cryptodataapi-mcp

{
  "mcpServers": {
    "cryptodataapi": {
      "command": "npx",
      "args": ["-y", "cryptodataapi-mcp"],
      "env": { "CRYPTODATA_API_KEY": "cdk_live_YOUR_KEY" }
    }
  }
}

Every data tool needs a key in the X-API-Key header. The Free tier needs no card and covers the whole market picture (see tiers below). Grab one at cryptodataapi.com/login, or POST an email to the auth endpoint — the key is returned once.

Agents can also bootstrap themselves: the server exposes a create_free_api_key tool that mints a free key from an email with no signup. And a few discovery tools (create_free_api_key, list_capabilities, get_exchange_links) need no key at all, so an agent can orient before it has one.

For autonomous upgrades, agents can self-subscribe over x402 (gasless USDC) via POST /api/v1/payments/agent-subscribe — no human in the loop.

curl -X POST https://cryptodataapi.com/api/v1/auth/keys \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]"}'

The server exposes ~24 curated, read-only tools (the heavy /backtesting/* bulk endpoints are intentionally left off — use the REST API for those). Grouped:

Prices & coins: get_price, get_coin_profile, get_top_coins, search_coins, get_hyperliquid_prices.

Market intelligence: get_daily_snapshot (one-call overview), get_market_health, get_market_regime (Pro), get_cycle_regime, get_fear_greed, get_macro, get_stablecoins, get_etf_flows.

Derivatives & positioning: get_funding_rates, get_open_interest, get_liquidations, get_order_book, get_positioning (Pro), get_gamma_exposure (Pro), get_whale_activity (Pro).

Utility & discovery: create_free_api_key, list_capabilities, get_exchange_links, and query_api — an escape hatch that calls any other GET endpoint across the 180+ endpoint REST surface. Start a session with get_daily_snapshot or list_capabilities.