hive-mcp-server
https://mcp.hiveintelligence.xyz
Registry code: a4401fc86d64a68a
Hive serves live crypto market data to AI agents over a compact 8-tool root. Loop: search_tools -> get_api_endpoint_schema -> invoke_api_endpoint for reads (invoke_stateful_endpoint only after explicit user approval; validate_task_result before structured answers). Every material response carries a _hive receipt (provider, fetched_at, runtime_status, _hive.receipt_id); cite it when answering. For the three dominant intents call the hero tools directly: get_token_price, check_token_safety, get_wallet_portfolio (response_format "concise" default, "detailed" available). Degraded providers are…
- endpoint
- https://mcp.hiveintelligence.xyz/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is hive-mcp-server live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is hive-mcp-server free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does hive-mcp-server have?
- 8 tools: invoke_api_endpoint, validate_task_result, invoke_stateful_endpoint, get_wallet_portfolio, get_api_endpoint_schema, search_tools, check_token_safety, get_token_price.
- Is hive-mcp-server safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.8%· all time 98.8%
last good check
of 8 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get a token price
- check a token contract for safety
- view a wallet's token portfolio
- discover crypto data endpoints
- takes → gives
- text, data → data
- tools
- 7 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_tools reads open 5d ago
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 each exact schema. Execute reads with invoke_api_endpoint and explicitly approved Hive state changes with invoke_stateful_endpoint.
{ "type": "object", "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Maximum tools to return. Default 20." }, "query": { "type": "string", "maxLength": 512, "description": "Search text matched against tool name, title, category, provider, and summary." }, "cursor": { "type": "string", "description": "Pagination cursor from the previous response." }, "detail": { "enum": [ "compact", "standard", "full" ], "type": "string", "description": "Toolset detail level. Defaults to compact. Use full only when the task output schema is needed." }, "category": { "type": "string", "maxLength": 128, "description": "Optional category filter, for example Portfolio & Wallet." }, "provider": { "type": "string", "maxLength": 128, "description": "Optional provider filter such as CoinGecko, Moralis, Tenderly, Helius, GoPlus, CCXT, Alchemy, DeFiLlama, Hyperliquid, or Open Data Fetch." }, "route_id": { "type": "string", "maxLength": 100, "description": "Optional exact task-shaped route id. Use the matched route's ordered calls and conditional fallbacks instead of choosing from the coverage catalog." }, "toolset_id": { "type": "string", "maxLength": 100, "description": "Optional exact canonical task toolset id. Use this after an initial compact result to inspect one workflow." }, "toolset_limit": { "type": "integer", "maximum": 5, "minimum": 1, "description": "Maximum matching task toolsets to return. Default 3, max 5." }, "evidence_phase": { "type": "string", "maxLength": 100, "description": "Optional exact workflow evidence phase. Supported values: activity, alerts, approvals, assets, authenticity, balances, blocks, bridges, derivatives, discovery, enrichment, evidence, fees, funding, gas, history, holders, identity, infrastructure, liquidity, logs, market, markets, memory, monitoring, ohlcv, owners, positions, reports, risk, routing, sales, schema, simulation, stablecoins, trades, transactions, tvl, yields." }, "toolset_cursor": { "type": "string", "description": "Pagination cursor for task toolset matches." }, "response_format": { "enum": [ "json", "markdown" ], "type": "string", "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text." } }, "additionalProperties": false }arguments 73 linescheck_token_safety reads auth-required 16h ago
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 with plain-language verdicts. EVM chains use chain + address; Solana addresses are detected automatically.
{ "type": "object", "properties": { "chain": { "type": "string", "maxLength": 40, "description": "Chain name or EVM chain id, for example \"eth\", \"bsc\", \"8453\", or \"solana\". Defaults to eth for 0x addresses; Solana is auto-detected." }, "address": { "type": "string", "maxLength": 100, "minLength": 1, "description": "Required. Token contract address (0x… for EVM, base58 for Solana)." }, "response_format": { "enum": [ "concise", "detailed", "json", "markdown" ], "type": "string", "description": "concise (default) returns the trimmed essentials; detailed returns the full provider payload. json and markdown, the platform-wide values every other tool advertises, are accepted and treated as concise." } }, "additionalProperties": true }arguments 27 linesget_token_price reads auth-required 16h ago
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 provenance.
{ "type": "object", "properties": { "chain": { "type": "string", "maxLength": 40, "description": "Chain name for the contract-address variant, for example \"eth\", \"base\", \"bsc\", or \"solana\"." }, "token": { "type": "string", "maxLength": 100, "minLength": 1, "description": "CoinGecko coin id or ticker symbol, for example \"bitcoin\" or \"BTC\". Omit when passing chain + address." }, "address": { "type": "string", "maxLength": 100, "description": "Token contract address; requires chain." }, "vs_currency": { "type": "string", "maxLength": 20, "description": "Quote currency. Default \"usd\"." }, "response_format": { "enum": [ "concise", "detailed", "json", "markdown" ], "type": "string", "description": "concise (default) returns the trimmed essentials; detailed returns the full provider payload. json and markdown, the platform-wide values every other tool advertises, are accepted and treated as concise." } }, "additionalProperties": true }arguments 37 linesinvoke_api_endpoint reads unknown 5d ago
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 invoke_stateful_endpoint after explicit user approval.
{ "type": "object", "properties": { "args": { "type": "object", "description": "The arguments to pass to the endpoint. This must match the schema returned by the `get_api_endpoint_schema` tool. You may also pass arguments as flat top-level keys alongside endpoint_name.", "propertyNames": { "type": "string" }, "additionalProperties": {} }, "endpoint": { "type": "string", "description": "Alias for 'endpoint_name', accepted by both root invokers. Provide one of the two." }, "endpoint_name": { "type": "string", "description": "The name of the endpoint to invoke." }, "response_format": { "enum": [ "json", "markdown" ], "type": "string", "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text." } }, "additionalProperties": {} }arguments 30 linesvalidate_task_result reads unknown 5d ago
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, conditional fallback use, the four-call route budget, claim-to-receipt citations, canonical phase coverage, and internal receipt consistency. It cannot authenticate invented receipts or turn SHA-256 self-checks into signatures, so every call entry must be copied exactly from the server-minted _hive block returned by that execution.
{ "type": "object", "required": [ "task_toolset_id", "result" ], "properties": { "result": { "type": "object", "description": "The proposed task result envelope. Each receipt.calls entry must be copied exactly from a material call's _hive object.", "propertyNames": { "type": "string" }, "additionalProperties": {} }, "response_format": { "enum": [ "json", "markdown" ], "type": "string", "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text." }, "task_toolset_id": { "type": "string", "description": "Canonical task toolset id returned by search_tools." } }, "additionalProperties": false }arguments 30 linesinvoke_stateful_endpoint changes data unknown never probed
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 auto-approve it. Inspect get_api_endpoint_schema first and verify the saved result after execution.
{ "type": "object", "properties": { "args": { "type": "object", "description": "The arguments to pass to the endpoint. This must match the schema returned by the `get_api_endpoint_schema` tool. You may also pass arguments as flat top-level keys alongside endpoint_name.", "propertyNames": { "type": "string" }, "additionalProperties": {} }, "endpoint": { "type": "string", "description": "Alias for 'endpoint_name', accepted by both root invokers. Provide one of the two." }, "endpoint_name": { "type": "string", "description": "The name of the endpoint to invoke." }, "response_format": { "enum": [ "json", "markdown" ], "type": "string", "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text." } }, "additionalProperties": {} }arguments 30 linesget_wallet_portfolio reads unknown 5d ago
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 are detected automatically and route through Helius.
{ "type": "object", "properties": { "chain": { "type": "string", "maxLength": 40, "description": "Chain name, for example \"eth\", \"base\", \"arbitrum\", or \"solana\". Defaults to eth for 0x addresses; Solana is auto-detected." }, "address": { "type": "string", "maxLength": 100, "minLength": 1, "description": "Required. Wallet address (0x… for EVM, base58 for Solana)." }, "include_spam": { "type": "boolean", "description": "Show likely spam airdrops (tokens with a URL or claim lure in the name, and on EVM chains tokens with no market price). Default false; the response says how many were hidden." }, "response_format": { "enum": [ "concise", "detailed", "json", "markdown" ], "type": "string", "description": "concise (default) returns the trimmed essentials; detailed returns the full provider payload. json and markdown, the platform-wide values every other tool advertises, are accepted and treated as concise." } }, "additionalProperties": true }arguments 31 linesget_api_endpoint_schema reads unknown 4d ago
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.
{ "type": "object", "properties": { "endpoint": { "type": "string", "description": "The name of the endpoint to get the schema for." }, "endpoint_name": { "type": "string", "description": "Alias for 'endpoint', accepted for symmetry with invoke_api_endpoint. Provide one of the two." }, "response_format": { "enum": [ "json", "markdown" ], "type": "string", "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text." } }, "additionalProperties": true }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida4401fc86d64a68a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a4401fc86d64a68a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a4401fc86d64a68a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- www.hiveintelligence.xyz
- docs.hiveintelligence.xyz Hive Intelligence