Sato Hub
MCP

Hive Intelligence Crypto MCP

Hosted MCP exposing 375+ crypto tools spanning market data, DeFi analytics, security scans, and wallet data.

  • Sato Score65
  • ChainsMultichain
ActiveSelf-Reported

Hive Intelligence Crypto MCP is a closed-source MCP server by Hive Intelligence, with no code activity tracked. Sato Score 65/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Hive Intelligence Crypto MCP →

No code activity tracked

Listed from hiveintelligence.xyz on 2026-07-12. Install: not attempted. Evidence →

Next step

Watch Hive Intelligence Crypto MCP

One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on https://mcp.hiveintelligence.xyz/mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Hive Intelligence operates a managed MCP server that normalizes access to multiple crypto data providers behind a single interface — market prices/OHLC, DeFi TVL/yields, token security and rug-pull risk scans, DEX pool/liquidity data, wallet balances and PnL, Solana-native RPC, exchange spot/perps data, and Polymarket prediction-market data. Agents authenticate with a Hive API key (Bearer token) and are billed on a credit system, one credit per tool call regardless of underlying provider. Works with Claude, Cursor, OpenAI, and Gemini-based agents.

Sato Score

65/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
0/20
Interface verifiability
10/10
Docs & demo
6/10
Listing transparency & provenance
11/15
Independent verification
3/10

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Evidence — listed vs checked · what the words mean

Listed from hiveintelligence.xyz on 2026-07-12. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedhiveintelligence.xyzas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedhiveintelligence.xyzas of 2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedhiveintelligence.xyzas of 2026-07-20
MCP endpoint answersanswered — 8 tools listedobservedmcp.hiveintelligence.xyz2026-10-15
Daily check record44 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asHosted (managed remote MCP server, no self-hosting)confidence 0.85self-reportedhiveintelligence.xyzas of 2026-07-14
Works withClaude, Cursor, OpenAI Responses API, Gemini CLI, Windsurf, Codex CLI, VS Codeconfidence 0.85self-reportedhiveintelligence.xyzas of 2026-07-14
Sato Score65/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: Hosted MCP endpoint (no local install)

claude mcp add --transport http hive "https://mcp.hiveintelligence.xyz/mcp" --header "Authorization: Bearer YOUR_HIVE_API_KEY"
{"mcpServers": {"hive": {"url": "https://mcp.hiveintelligence.xyz/mcp", "headers": {"Authorization": "Bearer YOUR_HIVE_API_KEY"}}}}

You supply: Hive API key (Bearer header; generated in the Hive dashboard)

Add to CursorAdd to VS Code
claude mcp add --transport http satohub-hive-intelligence-mcp https://mcp.hiveintelligence.xyz/mcp

A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-20. What a deploy spec is →

Tool inventory — 8 tools, probed live 2026-10-15

  • get_token_price — Current price for one token. Pass token as a CoinGecko id or symbol ("bitcoin", "BTC"), or pass chain + address for a specific contract. Returns price, market cap, and 24h change with provider provena
  • check_token_safety — Token security screen for a contract address: honeypot, taxes, ownership, and related GoPlus risk datapoints, plus a summary of LP lock status, top-holder concentration, and creator/owner balances wit
  • get_wallet_portfolio — Token holdings for a wallet with balances and USD values where available. Likely spam airdrops are hidden and counted (include_spam=true shows them). EVM chains route through Alchemy; Solana wallets a
  • search_tools — Search canonical task toolsets, compact user-intent routes, and the full Hive coverage catalog. Select a matching route first, follow its ordered primary calls and conditional fallbacks, then inspect
  • get_api_endpoint_schema — Returns the full input schema, operation type, and correct root invoker for any Hive tool by name. Tool names come from search_tools; inspect this contract before execution.
  • invoke_api_endpoint — Invokes only read-only Hive endpoints by name. First discover the tool, inspect get_api_endpoint_schema, and pass bounded schema-valid arguments. State-changing endpoints are rejected and must use inv
  • invoke_stateful_endpoint — Invokes a Hive-native state-changing endpoint after explicit user approval. This router can create, update, archive, remember, forget, acknowledge, or resolve durable Hive state, so clients must not a
  • validate_task_result — Validates a proposed workflow answer against Hive's typed task-output and evidence-receipt contract before it is shown to the user. It checks the selected route id, ordered route-only calls, condition
Answers a handshake
yes · 2026-10-15
Answers a call
yes — search_tools returned in 904 ms

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-17

100%of 45 checks since 2026-09-01 succeeded
Currently responding for 56 days
Succeeded
59
Failed
32
Their error
0
Unattributed
32

State changed on 2026-07-19 (responding → unclear), 2026-08-19 (unclear → responding), 2026-08-20 (responding → unclear), 2026-08-21 (unclear → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
8
from the server's own tools/list · 29/30 days
Sato Score
65
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
MCP Server, Data Provider
Open source
No
Pricing
Credit-based: one credit per tool call; plan limits and monthly credits per tier
Deploys as
Hosted (managed remote MCP server, no self-hosting)
Works with
Claude, Cursor, OpenAI Responses API, Gemini CLI, Windsurf, Codex CLI, VS Code
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#market-data#defi-analytics#security-scan#wallet-data#hosted-mcp
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Hive Intelligence Crypto MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Aug 21, 2026
    Sato Score tier: Low → Medium
    Score 35 → 62.
  2. Aug 20, 2026
    Sato Score tier: Medium → Low
    Score 62 → 35.
  3. Aug 19, 2026
    Sato Score tier: Low → Medium
    Score 25 → 62.
  4. Jul 20, 2026
    Edited: mcp endpoint url
  5. Jul 20, 2026
    Edited: deploy spec
  6. Jul 19, 2026
    Edited: mcp endpoint url
  7. Jul 18, 2026
    Sato Hub began tracking this listing
  8. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  9. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Hive Intelligence Crypto MCP

Is Hive Intelligence Crypto MCP open source?
No. Hive Intelligence Crypto MCP is closed source as of 2026-10-15.
Which chains does Hive Intelligence Crypto MCP support?
Hive Intelligence Crypto MCP lists support for Multichain as of 2026-10-15.
Is Hive Intelligence Crypto MCP still maintained?
Sato Hub tracks no commit or release for Hive Intelligence Crypto MCP; it cannot say whether it is maintained.
How do I install or run Hive Intelligence Crypto MCP?
Hosted MCP endpoint (no local install). Install: claude mcp add --transport http hive "https://mcp.hiveintelligence.xyz/mcp" --header "Authorization: Bearer YOUR_HIVE_API_KEY". Entry: {"mcpServers": {"hive": {"url": "https://mcp.hiveintelligence.xyz/mcp", "headers": {"Authorization": "Bearer YOUR_HIVE_API_KEY"}}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.hiveintelligence.xyz/mcp (Streamable HTTP)).
Is Hive Intelligence Crypto MCP verified on Sato Hub?
Sato Hub holds one earned check for Hive Intelligence Crypto MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 65 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Hive Intelligence Crypto MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/hive-intelligence-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.