Hive Intelligence MCP
Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.
- 1.9.0
- Version
- remote + npm
- Transport
- 8
- Tools
Security review
Review passedReviewed 1d ago.
- tools: 8 tools scanned
- metadata: scanned
- packages: 1 checked
No findings.
Tools (8)
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 provenance.
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 with plain-language verdicts. EVM chains use chain + address; Solana addresses are detected automatically.
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 are detected automatically and route through Helius.
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 each exact schema. Execute reads with invoke_api_endpoint and explicitly approved Hive state changes with invoke_stateful_endpoint.
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 invoke_stateful_endpoint after explicit user approval.
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 auto-approve it. Inspect get_api_endpoint_schema first and verify the saved result after execution.
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, 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.