Hive Intelligence MCP
REMOTE · MCP.HIVEINTELLIGENCE.XYZ · 2 COMPONENTS
Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.
Available components
Last scanned (53 minutes ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
Recent critical change
Authorization (30 Sept 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (invoke_stateful_endpoint). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2126 tokens (~141/item across 15 items; 8 tools + 7 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Server version: 1.17.1 → 1.17.2 functional
- 4 Nov 26 0
- Server version: 1.17.0 → 1.17.1 functional
- Server version: 1.16.1 → 1.17.0 functional
- “get_wallet_portfolio” reworded the description of “include_spam” cosmetic
- 3 Nov 26 0
- Server version: 1.16.0 → 1.16.1 functional
- 28 Oct 26 0
- Server version: 1.15.0 → 1.16.0 functional
- 26 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.14.0 → 1.15.0 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.13.1 → 1.14.0 functional
- 23 Oct 26 0
- Server version: 1.13.0 → 1.13.1 functional
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.12.1 → 1.13.0 functional
- Server version: 1.12.0 → 1.12.1 functional
- Server version: 1.11.2 → 1.12.0 functional
- “search_tools” reworded the description of “provider” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.hiveintelligence.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.hiveintelligence.xyz | CN=WR3,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | RSA 2048 | SHA256-RSA | bb1b22757732d42709b65780f5f10b38 |
| SANs: mcp.hiveintelligence.xyz | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.hiveintelligence.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| hiveintelligence.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self';form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self' 'nonce-f11de1c202e34ade9c45c01aa3b83e4d' https://www.googletagmanager.com https://cdn.tailwindcss.com;script-src-attr 'none';style-src 'self' 'unsafe-inline';upgrade-insecure-requests;connect-src 'self' https://www.google-analytics.com https://www.google.com;frame-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hiveintelligence.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.hiveintelligence.xyz/mcp | HTTPS enforced | 302 | https://mcp.hiveintelligence.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_token_safety Check Token Safety ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Required. Token contract address (0x… for EVM, base58 for Solana). |
| chain | string | – | Chain name or EVM chain id, for example "eth", "bsc", "8453", or "solana". Defaults to eth for 0x addresses; Solana is auto-detected. |
| response_format | string | – | 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 conc… |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| chain | string | – | – |
| holder_count | – | – | – |
| note | string | – | – |
| risk_flags | object | – | Raw provider risk datapoints; '1' means flagged. A missing key means the provider did not report that signal, not that it passed. |
| source_receipt | object | yes | – |
| summary | object | – | Concise scam signals: verdicts (plain-language list), lp (lock state and top LP holder), top_holders (largest holder and top-10 share, DEX pairs excluded), creator, owner. Percents are 0-100. |
| token_name | string | – | – |
No examples provided.
get_api_endpoint_schema API Endpoint Schema ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | – | The name of the endpoint to get the schema for. |
| endpoint_name | string | – | Alias for 'endpoint', accepted for symmetry with invoke_api_endpoint. Provide one of the two. |
| response_format | string | – | Output format: 'json' for structured data (default) or 'markdown' for human-readable text. |
| Name | Type | Req | Description |
|---|---|---|---|
| _hive | object | yes | – |
| annotations | object | – | – |
| callPattern | string | – | – |
| category | string | – | – |
| description | string | – | – |
| inputSchema | object | – | – |
| name | string | – | – |
| operation | string | – | – |
| outputSchema | object | – | – |
| provider | string | – | – |
| runtimeStatusSemantics | object | – | – |
| runtimeStatuses | array | – | – |
| title | string | – | – |
| toolsets | array | – | – |
No examples provided.
get_token_price Get Token Price ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Token contract address; requires chain. |
| chain | string | – | Chain name for the contract-address variant, for example "eth", "base", "bsc", or "solana". |
| response_format | string | – | 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 conc… |
| token | string | – | CoinGecko coin id or ticker symbol, for example "bitcoin" or "BTC". Omit when passing chain + address. |
| vs_currency | string | – | Quote currency. Default "usd". |
| Name | Type | Req | Description |
|---|---|---|---|
| change_24h_percent | number | – | – |
| market_cap | number | – | – |
| price | number | – | – |
| source_receipt | object | yes | – |
| token | string | – | – |
| vs_currency | string | – | – |
No examples provided.
get_wallet_portfolio Get Wallet Portfolio ~269
Token holdings for a wallet with balances, USD values, and 24h price change where available. Likely spam airdrops are hidden and counted (include_spam=true shows them). EVM chains route through CoinGecko (eth, base, bsc, polygon_pos, arbitrum, optimism, avax, linea, stable, robinhood, arc) with Alchemy as the fallback; Solana wallets are detected automatically and route through Helius.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Required. Wallet address (0x… for EVM, base58 for Solana). |
| chain | string | – | Chain name, for example "eth", "base", "arbitrum", or "solana". Defaults to eth for 0x addresses; Solana is auto-detected. |
| include_spam | boolean | – | Show likely spam airdrops (tokens with a URL or claim lure in the name, and on EVM chains tokens with no market price or not listed on CoinGecko). Default false; the response says how many were hidde… |
| response_format | string | – | 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 conc… |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| chain | string | – | – |
| note | string | – | – |
| source_receipt | object | yes | – |
| token_count | number | – | Total holdings found, which may exceed tokens.length. |
| tokens | array | – | Holdings; truncated in concise mode when note is present. |
No examples provided.
invoke_api_endpoint Invoke Read-only API Endpoint ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | 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. |
| endpoint | string | – | Alias for 'endpoint_name', accepted by both root invokers. Provide one of the two. |
| endpoint_name | string | – | The name of the endpoint to invoke. |
| response_format | string | – | Output format: 'json' for structured data (default) or 'markdown' for human-readable text. |
| Name | Type | Req | Description |
|---|---|---|---|
| _degraded | string | – | – |
| _hive | object | yes | – |
| _metadata | object | – | – |
| _pagination | object | – | – |
| _provider | string | – | – |
| _truncated | boolean | – | – |
| _type | string | – | – |
| data | – | – | Provider data payload when the response uses a data wrapper. |
| error | string | – | – |
| items | array | – | Array result when a provider returns a top-level list. |
| message | string | – | – |
| result | – | – | Provider result payload when the response uses a result wrapper. |
| status | – | – | Provider-reported status. Type varies by provider (string, boolean, or number), so no type constraint is applied. |
No examples provided.
invoke_stateful_endpoint Invoke Stateful Hive Endpoint ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | 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. |
| endpoint | string | – | Alias for 'endpoint_name', accepted by both root invokers. Provide one of the two. |
| endpoint_name | string | – | The name of the endpoint to invoke. |
| response_format | string | – | Output format: 'json' for structured data (default) or 'markdown' for human-readable text. |
| Name | Type | Req | Description |
|---|---|---|---|
| _degraded | string | – | – |
| _hive | object | yes | – |
| _metadata | object | – | – |
| _pagination | object | – | – |
| _provider | string | – | – |
| _truncated | boolean | – | – |
| _type | string | – | – |
| data | – | – | Provider data payload when the response uses a data wrapper. |
| error | string | – | – |
| items | array | – | Array result when a provider returns a top-level list. |
| message | string | – | – |
| result | – | – | Provider result payload when the response uses a result wrapper. |
| status | – | – | Provider-reported status. Type varies by provider (string, boolean, or number), so no type constraint is applied. |
No examples provided.
search_tools Search Tools ~430
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter, for example Portfolio & Wallet. |
| cursor | string | – | Pagination cursor from the previous response. |
| detail | string | – | Toolset detail level. Defaults to compact. Use full only when the task output schema is needed. |
| evidence_phase | string | – | Optional exact workflow evidence phase. Supported values: activity, alerts, approvals, assets, authenticity, balances, blocks, bridges, derivatives, discovery, enrichment, evidence, fees, funding, ga… |
| limit | integer | – | Maximum tools to return. Default 20. |
| provider | string | – | Optional provider filter such as CoinGecko, Tenderly, Helius, GoPlus, CCXT, Alchemy, DeFiLlama, Hyperliquid, or Open Data Fetch. |
| query | string | – | Search text matched against tool name, title, category, provider, and summary. |
| response_format | string | – | Output format: 'json' for structured data (default) or 'markdown' for human-readable text. |
| route_id | string | – | Optional exact task-shaped route id. Use the matched route's ordered calls and conditional fallbacks instead of choosing from the coverage catalog. |
| toolset_cursor | string | – | Pagination cursor for task toolset matches. |
| toolset_id | string | – | Optional exact canonical task toolset id. Use this after an initial compact result to inspect one workflow. |
| toolset_limit | integer | – | Maximum matching task toolsets to return. Default 3, max 5. |
| Name | Type | Req | Description |
|---|---|---|---|
| _hive | object | yes | – |
| category | string | – | – |
| pagination | object | – | – |
| provider | string | – | – |
| query | string | – | – |
| route_id | string | – | – |
| tools | array | – | – |
| toolset_detail | string | – | – |
| toolset_pagination | object | – | – |
| toolsets | array | – | – |
No examples provided.
validate_task_result Validate Task Result ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | Output format: 'json' for structured data (default) or 'markdown' for human-readable text. |
| result | object | yes | The proposed task result envelope. Each receipt.calls entry must be copied exactly from a material call's _hive object. |
| task_toolset_id | string | yes | Canonical task toolset id returned by search_tools. |
| Name | Type | Req | Description |
|---|---|---|---|
| _hive | object | yes | – |
| call_count | number | yes | – |
| errors | array | yes | – |
| receipt_ids | array | yes | – |
| route_id | string | yes | – |
| task_toolset_id | string | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Hive Intelligence MCP server?
Hive Intelligence MCP is a hosted endpoint at https://mcp.hiveintelligence.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.hiveintelligence.xyz
claude mcp add --transport http xyz-hiveintelligence-mcp 'https://mcp.hiveintelligence.xyz/mcp'
What is the Hive Intelligence MCP server?
Hive Intelligence MCP is listed in the public MCP registry as xyz.hiveintelligence/mcp. Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call. This page covers its hosted endpoint (https://mcp.hiveintelligence.xyz/mcp).
Is the Hive Intelligence MCP server safe to use?
Hive Intelligence MCP scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Hive Intelligence MCP server expose?
Hive Intelligence MCP exposes 8 tools: get_token_price, check_token_safety, get_wallet_portfolio, search_tools, get_api_endpoint_schema, and 3 more. Their descriptions and schemas cost roughly 1,729 tokens of context every time the server is loaded.
Does the Hive Intelligence MCP server require authentication?
No. We connected to Hive Intelligence MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hive Intelligence MCP server still maintained?
Hive Intelligence MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.