Try it now, with no account and no key. The hosted endpoint's anonymous lane answers 25 material calls per IP per day; discovery, schema lookup, and validation are always free:

text

Copy

https://mcp.hiveintelligence.xyz/mcp

Guided setup · Install guides · Example prompts

Connect

Hive is a hosted MCP server for clients that support remote Streamable HTTP. Once the hosted OAuth deployment is enabled, interactive clients discover it from the public endpoint and open browser authorization. Headless agents can use an API key from secret storage:

https://mcp.hiveintelligence.xyz/mcp

One-click config prefills, URL-only with no key or secret embedded:

The prefills carry only the public endpoint URL. The setup pages check the live protected-resource metadata, server card, release version, and required client redirect profiles before showing a native install action. Until that gate passes, use the API-key fallback from a trusted backend/client; never put a key in an install link. Per-client config blocks are below.

What is Hive Intelligence?

A managed MCP server, REST API, and CLI that give AI agents one evidence-backed workflow surface over live crypto market data, DeFi, wallets, token security, DEX flows, NFTs, and on-chain network data. Agents receive the provider, Hive retrieval time, Hive first-observation/original cache time, cache age, fallback state, runtime status, and a unique receipt for every material execution instead of silently mixing provider data.

Connect to your AI client

The hosted endpoint is the same everywhere. After OAuth activation, interactive clients should start with URL-only OAuth discovery. API-key auth remains the explicit headless fallback.

Claude Code

claude mcp add --transport http --scope user hive https://mcp.hiveintelligence.xyz/mcp

Or install the full plugin bundle (the hosted MCP connection plus 16 crypto workflow skills) from this repository's plugin marketplace:

claude plugin marketplace add hive-intel/hive-sdk
claude plugin install hive@hive

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

{
  "mcpServers": {
    "hive": {
      "url": "https://mcp.hiveintelligence.xyz/mcp"
    }
  }
}

VS Code (GitHub Copilot Chat)

.vscode/mcp.json (note the required type: "http"):

{
  "servers": {
    "hive": {
      "type": "http",
      "url": "https://mcp.hiveintelligence.xyz/mcp"
    }
  }
}

Claude Desktop

Claude Desktop uses the Custom Connectors UI for remote MCP. Open Settings → Connectors → Add custom connector, set the URL to https://mcp.hiveintelligence.xyz/mcp, then, after OAuth activation, complete browser authorization. Do not paste a remote url block into claude_desktop_config.json; that file is for local stdio servers.

Windsurf / Devin Desktop

Windsurf uses serverUrl (not Cursor's url) in ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "hive": {
      "serverUrl": "https://mcp.hiveintelligence.xyz/mcp"
    }
  }
}

Gemini CLI

Gemini CLI requires httpUrl in ~/.gemini/settings.json:

{
  "mcpServers": {
    "hive": {
      "httpUrl": "https://mcp.hiveintelligence.xyz/mcp"
    }
  }
}

Both configs are URL-only and can use native OAuth after hosted OAuth activation. Full per-client guides: hiveintelligence.xyz/install.

Headless API-key fallback

For automation that cannot open a browser, keep a Hive API key in secret storage and send Authorization: Bearer $HIVE_API_KEY. Never embed a real key in an install link, shared config, screenshot, or repository.

Local stdio (self-host / desktop / your own provider keys)

Prefer a local process or your own upstream keys? Run the published CLI as a stdio MCP server:

{
  "mcpServers": {
    "hive": {
      "command": "npx",
      "args": ["-y", "-p", "hive-intelligence@latest", "hive"],
      "env": {
        "COINGECKO_DEMO_API_KEY": "optional",
        "ALCHEMY_API_KEY": "optional",
        "HELIUS_API_KEY": "optional",
        "MORALIS_API_KEY": "optional"
      }
    }
  }
}

Local stdio does not use a hosted HIVE_API_KEY; configure only the upstream provider keys you want that local process to call. Keyless providers remain available and providers without credentials stay discoverable with a classified missing_key runtime status. hive-intelligence is a stdio transport (a JSON-RPC channel, not an interactive command). For terminal use, see the CLI.

Authentication

• No key needed to start: the hosted endpoint's anonymous lane answers 25 material calls per IP per day, and discovery/schema/validation calls are always free.
• Get a key at hiveintelligence.xyz/dashboard/keys when you want your own quota; the Free plan needs no card.
• Authenticate the hosted endpoint with Authorization: Bearer hive_live_... (legacy alias x-api-key also works).
• One key, least privilege: keys are scoped to your plan's rate limit and credits. Rotate or revoke from the dashboard; never commit a key or paste it into client-side code.

Powered by

Eleven upstream provider integrations plus Open Data Fetch, normalized into one tool surface:

Alchemy · CoinGecko · DeFiLlama · Moralis · GoPlus · Helius · Tenderly · CCXT · Hyperliquid · RWA Perps · Hive Archive · Open Data Fetch

Tools & discovery

Hive's default contract is a compact eight-tool root: three hero tools for the dominant intents, plus a five-tool discovery/execution loop over the full catalog.