Hive Intelligence home
Hive Intelligence
GitHub

One connection for evidence-backed crypto due diligence.

Every answer comes with sources, freshness, and a runtime receipt.

Try a live diligence checkChoose your AI client

Discover the taskinspect the schemaexecute a bounded callpreserve the receipt

Native remote MCP in Claude, Cursor, VS Code, Windsurf, ChatGPT, Grok, and Gemini CLI. API-key fallbacks cover headless agents.

agent-answer.json
runtime-receipt
{
  "question": "Is this token safe to research further?",
  "decision": "pass | block | escalate",
  "evidence": [
    { "source": "token security provider", "finding": "..." },
    { "source": "DEX liquidity provider", "finding": "..." }
  ],
  "runtime_receipt": {
    "provider": "shown per tool result",
    "provider_evidence_time": "timestamp | block | slot | unknown",
    "fetched_at": "Hive retrieval completion",
    "observed_at": "Hive first observation",
    "cache_age_ms": "Hive cache age",
    "runtime_status": "ok | degraded | unavailable",
    "receipt_id": "server-issued UUID",
    "receipt_version": "1.0"
  }
}

Start with the path that matches your job

Hive is a due-diligence workflow layer, a managed MCP server, and a direct API. You do not need to learn the full catalog first.

No account for fixed demo
Run a diligence check
Inspect a live, read-only price, risk, TVL, or yield workflow before you install anything.
Try the live demo
MCP client paths
Use Hive inside an AI agent
Use OAuth remote MCP in supported chat and coding clients, or an explicit API-key fallback for headless agents.
Compare client setup
MCP · REST · CLI
Build a crypto-aware product
Start with task discovery, inspect exact schemas, execute bounded calls, and preserve provenance in your UI.
Open the builder path

Documented integration paths

Claude Code
Claude CodeNative remote MCP
Cursor
CursorNative remote MCP
ChatGPT / OpenAI
ChatGPT / OpenAIOAuth MCP + API
Gemini CLI
Gemini CLINative remote MCP
LangChain
LangChainApplication adapter

Published where agents discover tools

Canonical public records point to the hosted endpoint, public SDK, and installable CLI.

Official MCP Registryxyz.hiveintelligence/mcpnpm CLI + stdiohive-intelligence (verify published version)Public SDK repositoryhive-intel/hive-sdkServer discovery cardmachine-readable metadata

License note: the public hive-intelligence package currently reports UNLICENSED metadata; the typed client adapter and public skill packs are MIT-licensed, while the hosted managed server is proprietary infrastructure.

News coverage

Links include coverage and syndicated launch announcements; each opens the original publication page.

BenzingaBusiness InsiderDecryptThe StreetInvesting.comThe DefiantBinanceFinboldThe Fintech MagCrypto Briefing

Hive Intelligence gives AI agents one connection for evidence-backed crypto due diligence. Start with a live read-only workflow, then connect a compatible client to https://mcp.hiveintelligence.xyz/mcp and preserve provider, freshness, and runtime metadata in every answer.

Try the live demo → Choose an AI client See live catalog

Every answer comes with sources, freshness context, and a runtime receipt. Interactive clients use URL-only OAuth when the live readiness check passes; API keys remain the headless fallback.

Run a diligence workflow

Try a fixed read-only live workflow without an account, then bring your own key for custom tools.

Choose an AI integration

Compare native remote MCP, local stdio, and API-bridge paths without overstating direct UI compatibility.

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
Interactive authAdd only the URL, then complete OAuth in the browser
Headless/API fallbackAuthorization: Bearer YOUR_HIVE_API_KEY from secret storage
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, provider-backed price data, provider-native evidence time when available, runtime_status, and receipt_id/receipt_version.

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.

Secondary technical inventory: the source-backed catalog spans 10 category endpoints, 519 provider tools, and 18 Hive-native stateful tools. Use live discovery to confirm deployed availability before execution.

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

  • For headless, REST, CLI, and automation paths, store Hive API keys in environment variables or a secret manager. Interactive OAuth clients should not receive a key in shared config.
  • 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