Hive Intelligence home
Hive Intelligence
GitHub

Crypto data infrastructure for AI agents.

One managed MCP server and REST API for live prices, wallets, DeFi analytics, token risk, NFTs, networks, and prediction markets.

Get an API keyOpen setup

9 providers10 categories369 callable tools

Works with Claude, Cursor, OpenAI, and Codex.

index.js
package.json
const response = await fetch(
  "https://mcp.hiveintelligence.xyz/api/v1/execute",
  {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      Authorization: `Bearer ${process.env.HIVE_API_KEY}`,
    },
    body: JSON.stringify({
      tool: "get_price",
      args: { ids: "bitcoin,ethereum" }
    })
  }
);

Works with major AI platforms

Claude AICursor IDEChatGPTGoogle GeminiLangChain

As featured in

BenzingaBusiness InsiderDecryptThe StreetInvesting.comThe DefiantBinanceFinboldThe Fintech MagFinsmesCrypto Briefing

Hive Intelligence exposes live crypto data through a managed remote MCP server, REST API, and CLI. Start by connecting one supported client to https://mcp.hiveintelligence.xyz/mcp, authenticate with a Hive API key, verify one live tool call, then choose the integration surface your agent or application should use.

Get Started → Get an API key See live catalog

9 providers · 10 categories · 369 callable tools · runs in Claude Desktop, Claude Code, Cursor, OpenAI Responses API, Windsurf, VS Code, Codex CLI, and Gemini CLI

Get Started

Get a key, connect a client, verify one live tool call, inspect discovery, and choose the right production surface.

Install in an AI Client

Use client-specific setup guides for Claude Desktop, Claude Code, Cursor, OpenAI Responses API, Codex, Gemini, Windsurf, and VS Code.

Get API Keys

Create a key for MCP, REST, CLI, and adapter requests. Plan limits control credits and rate limits.

Live Catalog

Search the current callable tool catalog and inspect the discovery surfaces agents should use.

Connect to Hive's remote MCP server

ItemValue
Remote MCP URLhttps://mcp.hiveintelligence.xyz/mcp
TransportStreamable HTTP
Auth headerAuthorization: Bearer YOUR_HIVE_API_KEY
Client setupInstall Hive or Client Setup

After connecting a client, ask it to use Hive tools for the current BTC and ETH prices in USD. Continue when the response shows a Hive tool call, live provider-backed price data, and metadata such as provider, fetched_at, and runtime_status.

For client-independent verification, run the REST smoke test in Get Started or Quick Start.

What your agent does with Hive

Query the market

Prices, volume, market caps, movers, and global stats. One execution contract across the venues your agent needs.

  • get_price
  • get_coins_market_data
  • get_global_stats

Watch the chain

Wallet balances, transaction history, DEX flows, DeFi positions, and protocol TVL. Onchain context through the same Hive execution contract.

  • get_defi_protocol
  • get_protocol_tvl
  • get_trending_pools
  • alchemy_get_token_balances_by_wallet
  • moralis_get_wallet_history

Screen for risk

Honeypot detection, contract risk, and rugpull signals — before your agent hands anything to a user to sign.

  • get_token_security
  • detect_rugpull

Track prediction markets

Discover markets, monitor price movements, and aggregate trade flow for reporting or agent ranking.

  • codex_prediction_market_stats
  • codex_prediction_event_stats
  • codex_prediction_trades

See the live catalog → Your agent discovers tools at runtime through MCP tools/list, hive://tools, category endpoints, or REST discovery. Supported guides cover Claude Desktop, Claude Code, Cursor, OpenAI Responses API, Windsurf, VS Code, Codex CLI, and Gemini CLI.

Discovery

bash
curl -X GET "https://mcp.hiveintelligence.xyz/api/v1/tools?limit=20" \
  -H "Authorization: Bearer YOUR_HIVE_API_KEY"

From MCP clients, also use:

  • hive://tools
  • hive://categories
  • hive://providers

Production setup

  • Store Hive API keys in environment variables or a secret manager.
  • Use live discovery before hard-coding tool names.
  • Show source/provider, freshness, and runtime status when returning answers.
  • Handle 401, 429, provider unavailability, and degraded runtime status explicitly.
  • Use token security and risk tools before workflows that could lead a user to sign or swap.

Next Steps