MCP Server

The remote server speaks streamable HTTP at https://cryptodataapi.com/mcp. Recommended: add it with no API key. On the first tool call your client opens a browser, you sign in at cryptodataapi.com and click Authorize, and you're connected — no key is ever pasted into a terminal or an AI chat. New here? Signing in creates a free-tier account automatically, so there's nothing to set up first.

Browser login works in any MCP client that supports OAuth — Claude Code, Claude Desktop, Claude (web), Cursor, Windsurf, and more. The exact add command for each client is on its own page: Claude Code, Claude Desktop, Claude (web), Cursor, OpenAI Codex, Gemini CLI, Windsurf and GitHub Copilot.

Advanced — bring your own key. For clients that don't support OAuth, headless/automation setups, or to pin a specific key, authenticate with an X-API-Key header instead. Keep the secret in your shell environment and pass a placeholder so it never lands in chat logs or ~/.claude.json: export CRYPTODATA_API_KEY=... once, then add with --header 'X-API-Key: ${CRYPTODATA_API_KEY}' (single-quoted; expanded at connect time). Run install commands in your terminal, not an AI chat; rotate from the dashboard if a key leaks.

claude mcp add --transport http cryptodataapi \
  https://cryptodataapi.com/mcp
# first tool call opens a browser to sign in & authorize — no key pasted

export CRYPTODATA_API_KEY="cdk_live_YOUR_KEY"   # terminal only, never an AI chat
claude mcp add --transport http cryptodataapi \
  https://cryptodataapi.com/mcp \
  --header 'X-API-Key: ${CRYPTODATA_API_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" }
    }
  }
}

With browser login you don't need a key at all — signing in uses (or creates) your account at the Free tier (no card; covers the whole market picture, see tiers below). You only need an X-API-Key for the advanced header path: grab one at cryptodataapi.com/login, or POST an email to the auth endpoint — the key is returned once.

Agents can also bootstrap themselves with zero credentials: create_free_api_key is callable before you've connected with a key or an OAuth login at all — call it directly to mint a free key from an email, then reconnect with that key (every other tool, including list_capabilities, needs 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 26 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).

Account & discovery: create_free_api_key (no key needed), check_key_status, resend_verification_email, 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.