Crypto MCP Server

Hive Intelligence is the managed crypto MCP server for AI agents. One endpoint federating 9 providers — Alchemy, CoinGecko, DeFiLlama, GoPlus, Codex, CCXT, Helius, Tenderly, Moralis — across live prices, DeFi analytics, wallet intelligence, token security, DEX activity, and prediction markets. Connect Claude, Cursor, OpenAI Responses API, or another supported MCP client with one API key. Free Demo tier includes 10,000 monthly credits and every tool.

Start free with 10K credits → Try it in the playground

A Crypto MCP Server is a Model Context Protocol endpoint that connects AI agents — Claude, Cursor, OpenAI Responses API, Gemini, Windsurf, Codex — to live crypto market and on-chain data. Hive runs the server so you don't have to manage upstream auth, rate-limit handling, schema normalization, or provider integration code. You get one API key and one credit currency.

Why a managed Crypto MCP server

Rolling your own crypto data layer means stitching together separate provider APIs, each with its own authentication, rate limits, response shapes, pagination model, and error codes. Hive replaces that patchwork with one MCP connection:

• One API key across every data surface Hive normalizes.
• Runtime tool discovery -- your agent uses root tools/list, hive://tools, category endpoints, and REST discovery rather than hard-coding function definitions.
• One credit currency -- every tool call costs one credit regardless of which data surface serves it.
• Deterministic tool names and stable input schemas designed for LLM function calling, not human REST consumption.
• Standardized error codes -- your agent handles 4xx/5xx consistently across every tool.

If you are shipping a research agent, a trading bot, a wallet analyzer, or a security scanner, this is the data connection point.

Quick start

# Claude Code
claude mcp add --transport http hive "https://mcp.hiveintelligence.xyz/mcp" \
  --header "Authorization: Bearer YOUR_HIVE_API_KEY"

Full Claude integration guide has Claude Desktop, Cursor, and Claude API setups. For LangChain and CrewAI, see the MCP integration tutorial.

Coverage

369 callable tools, one root discovery endpoint, and ten capability-focused provider-category surfaces:

Every capability is callable through root invoke_api_endpoint, category-scoped MCP endpoints, or REST execution. See Data Coverage for full scope.

What the Hive MCP Server exposes

The Hive MCP server speaks the Model Context Protocol over Streamable HTTP. GET probes return an SSE-compatible response for clients that check transport availability before POSTing JSON-RPC. Dedicated setup guides cover Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, OpenAI Responses API, Codex CLI, and Gemini CLI; other clients must support Streamable HTTP plus API-key headers (Authorization: Bearer recommended, x-api-key legacy) to connect and discover Hive's tool surface at runtime.

• Root MCP endpoint: POST https://mcp.hiveintelligence.xyz/mcp
• 10 category-scoped MCP endpoints (e.g. /hive_market_data/mcp, /hive_security_risk/mcp)
• 369 callable tools in the full catalog: 351 categorized provider tools plus 18 Hive-native stateful tools
• Hundreds of direct category tools on the category endpoints
• Runtime discovery via tools/list, hive://tools, hive://toolsets, hive://task-canaries, and hive://skills
• Transport: Streamable HTTP (JSON-RPC over HTTP)

The server is a managed layer in front of a unified data fabric. Your agent pays one credit per tool call regardless of which underlying dataset serves it.

Root endpoint vs category endpoints

Hive exposes the same tool catalog through two shapes. Pick based on how focused your agent is.

Root /mcp

Use the root endpoint when your agent needs discovery, schema lookup, and access to the broader live catalog. This is the right default for general-purpose agents that may reach into any category.

• Compact 13-tool tools/list for discovery and execution routing
• hive://tools, hive://categories, hive://providers, hive://toolsets, hive://task-canaries, hive://skills, and hive://status discovery resources
• get_api_endpoint_schema for on-demand parameter lookup
• invoke_api_endpoint to execute exact callable tools

Category-scoped endpoints

Use category endpoints when you want a smaller, sharper tool surface. This improves tool-selection accuracy for LLM agents by eliminating irrelevant choices.

Agents can connect to more than one category endpoint simultaneously. A "market + security" agent, for example, can wire up /hive_market_data/mcp and /hive_security_risk/mcp together and ignore everything else.

Authentication

Every request to the MCP server or the REST execute surface needs an API key. Use either header shape:

• Authorization: Bearer YOUR_HIVE_API_KEY (recommended)
• x-api-key: YOUR_HIVE_API_KEY (legacy alias, also accepted)

API keys are created and rotated from the dashboard. The Free Demo tier includes 5 keys and 10,000 monthly credits.

Discovery resources

Read these from the root endpoint to understand what is available before you call anything:

• hive://tools -- the full live tool inventory (name, description, input schema)
• hive://categories -- the 10 category namespaces and their endpoints
• hive://providers -- the 9 active provider integrations and what each contributes
• hive://toolsets -- task routing maps for market, token, wallet, security, DEX, DeFi, NFT, Solana, network, prediction, search/discovery, and stateful monitoring workflows
• hive://task-canaries -- representative calls for checking that task-level workflows are healthy
• hive://skills -- install and workflow skill pack metadata for agents
• hive://status -- runtime states such as missing_key, plan_required, rate_limited, and degraded
• get_api_endpoint_schema -- on-demand parameter lookup for any tool

These are the authoritative, runtime-facing views from the live server and should be preferred over any static documentation your agent may have cached.

Example MCP call

curl -X POST https://mcp.hiveintelligence.xyz/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer YOUR_HIVE_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "invoke_api_endpoint",
      "arguments": {
        "endpoint_name": "get_price",
        "args": {
          "ids": "bitcoin",
          "vs_currencies": "usd"
        }
      }
    },
    "id": 1
  }'

Example client configuration

Claude Desktop

Claude Desktop adds remote MCP servers through Settings → Connectors → Add custom connector. Do not paste a url+headers block into claude_desktop_config.json; that file is for stdio servers.

Name: Hive
URL: https://mcp.hiveintelligence.xyz/mcp
Authentication: Bearer token
Token: YOUR_HIVE_API_KEY

Cursor

{
  "mcpServers": {
    "hive": {
      "url": "https://mcp.hiveintelligence.xyz/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HIVE_API_KEY"
      }
    }
  }
}

Claude Code

claude mcp add --transport http hive "https://mcp.hiveintelligence.xyz/mcp" \
  --header "Authorization: Bearer YOUR_HIVE_API_KEY"

Related

• Quick Start
• API Integration
• Tools Reference
• Live Catalog
• Data Sources
• MCP Features