hive-intelligence
v1.1.4
Published
Crypto MCP server and CLI for AI agents: 369 tools for market data, wallets, DeFi, DEX, NFTs, token risk, Solana, prediction markets, and stateful monitoring.
Maintainers
Readme
Hive Intelligence
Crypto intelligence for AI agents, shipped as a hosted MCP server, local
stdio MCP runtime, CLI, and REST API.
Hive gives Claude Code, Cursor, VS Code, OpenAI Responses API, Gemini CLI, Codex, and supported custom agents one compact way to discover and call live crypto data. Agents route through task toolsets, inspect schemas before execution, keep calls bounded, and return provider provenance plus runtime status instead of browsing a wall of raw endpoints.
npx -y -p hive-intelligence@latest hive init --all --browserUse the hosted MCP when you want Hive to run auth, rate limits, provider
infrastructure, and runtime status. Use local stdio when you want desktop
client setup, self-hosting, or provider-key experiments.
What You Get
- 369 tools across market data, wallets, DeFi, DEX, NFTs, token and contract data, security risk, network infrastructure, search, Solana, and prediction markets, including Hive-native stateful monitoring tools.
- A compact root MCP endpoint with 13 discovery/execution tools, so agents can route before they call.
- Task toolsets for market research, token diligence, wallet investigation, security checks, DEX pool analysis, DeFi research, NFT research, Solana analysis, network infrastructure, prediction markets, and stateful monitoring.
- CLI commands for auth, client setup, tool discovery, schema inspection, direct execution, diagnostics, aliases, polling, and config generation.
- Runtime resources for providers, categories, full tool catalog, task toolsets, canaries, skills, and status metadata.
- Bundled agent skills that teach assistants the right Hive workflow: discovery -> schema lookup -> bounded execution -> provenance-aware answer.
Quickstart
Requirements:
- Node.js 20+
- npm
- A Hive API key for hosted MCP or REST API
Create a key:
https://www.hiveintelligence.xyz/login?next=/dashboard/keysLog in and configure your local AI clients:
npx -y -p hive-intelligence@latest hive auth login
npx -y -p hive-intelligence@latest hive init --all --browserMake a first successful call:
npx -y -p hive-intelligence@latest hive market price --ids bitcoin --vs usd --jsonExpected output shape:
{
"ok": true,
"data": {
"bitcoin": {
"usd": 0
}
},
"meta": {
"provider": "CoinGecko",
"duration_ms": 0
}
}Use --json for scripts and agents. Use --pretty for human-readable output.
Connect Hosted MCP
One-click install, then replace YOUR_HIVE_API_KEY with your key from
hiveintelligence.xyz (the deep link cannot carry
your secret):
Hosted MCP URL:
https://mcp.hiveintelligence.xyz/mcpClaude Code:
claude mcp add --transport http --header "Authorization: Bearer YOUR_HIVE_API_KEY" hive https://mcp.hiveintelligence.xyz/mcpGeneric MCP JSON for clients that support remote HTTP and custom headers:
{
"mcpServers": {
"hive": {
"url": "https://mcp.hiveintelligence.xyz/mcp",
"headers": {
"Authorization": "Bearer YOUR_HIVE_API_KEY"
}
}
}
}Client Compatibility
| Client | Hosted HTTP MCP | Custom auth headers | Local stdio | Recommended setup |
| --- | --- | --- | --- | --- |
| Claude Code | Yes | Yes | Yes | hive init --all --browser or claude mcp add ... |
| Cursor | Yes | Yes | Yes | hive config cursor or hive init --all --browser |
| VS Code | Yes | Yes | Yes | hive config vscode or hive init --all --browser |
| Windsurf | Yes | Yes | Yes | hive init --all --browser |
| Gemini CLI | Yes | Yes | Yes | hive init --all --browser |
| Codex | Yes | Yes | Yes | hive init --all --browser |
| OpenAI Responses API | Yes | Yes | No | Use a server-side remote MCP tools entry |
| ChatGPT developer-mode apps | Beta / auth-dependent | Requires OAuth-compatible auth | No | Use Responses API or an OAuth-compatible proxy until Hive exposes OAuth/CIMD |
| Claude.ai custom connectors/directory | Not yet | No static bearer-token flow | No | Requires OAuth-compatible auth; Hive does not implement OAuth/CIMD yet |
Header-based API key auth works today for clients or API surfaces that support custom headers or authorization tokens. Claude.ai custom connectors, directory submissions, and direct ChatGPT app connectors require OAuth-compatible auth, so they are planned separately from this API-key MCP path.
Run Local stdio MCP
Use local stdio when you want a self-hosted MCP process, local desktop config,
or your own upstream provider keys.
{
"mcpServers": {
"hive-local": {
"command": "npx",
"args": ["-y", "-p", "hive-intelligence@latest", "hive"],
"env": {
"COINGECKO_PRO_API_KEY": "optional",
"ALCHEMY_API_KEY": "optional",
"HELIUS_API_KEY": "optional",
"MORALIS_API_KEY": "optional"
}
}
}
}Running hive with no subcommand starts the stdio MCP server. hive-mcp
remains available as a backward-compatible binary alias.
Staying Current
The hosted MCP (https://mcp.hiveintelligence.xyz/mcp) is managed by Hive.
Local stdio installs are pinned to whatever your client last fetched, so:
- Keep
hive-intelligence@latestin your client config (as shown above) so each host restart re-resolves the newest version. - Run
hive upgradeto update a global install and clear the npx cache, then restart your MCP client to load it:
npx -y -p hive-intelligence@latest hive upgradehive checks npm for newer versions once a day and surfaces the result through
hive doctor and the MCP server instructions, so your agent can prompt you when
an update is available. Set HIVE_NO_UPDATE_CHECK=1 to disable the check.
Use The CLI
Search the catalog:
npx -y -p hive-intelligence@latest hive tools search "token risk"Inspect a schema before execution:
npx -y -p hive-intelligence@latest hive tools info get_priceCall a tool from the terminal:
npx -y -p hive-intelligence@latest hive market price --ids bitcoin --vs usd --jsonCheck setup and provider status:
npx -y -p hive-intelligence@latest hive doctor
npx -y -p hive-intelligence@latest hive statusGenerate client config:
npx -y -p hive-intelligence@latest hive config claude-code
npx -y -p hive-intelligence@latest hive config cursor
npx -y -p hive-intelligence@latest hive config vscodeHow Agents Should Use Hive
Hive is designed for retrieval-led agent work:
- Discover the task surface with
search_tools,hive://toolsets, orhive tools search. - Inspect exact parameters with
get_api_endpoint_schemaorhive tools info. - Execute through
invoke_api_endpoint, category tools, REST, or the CLI. - Preserve provider, freshness, cache,
_hive,meta, and runtime status in the final answer. - Keep reads bounded with
limit,page,per_page, oroffset.
This flow lets an agent answer questions like:
- "Is this token safe to buy?"
- "What changed in this wallet over the last week?"
- "Compare Aave and Curve by TVL, fees, chains, and risk."
- "Find active prediction markets for the next Fed decision."
- "Show the best pools for this token and explain liquidity risk."
- "Remember this wallet monitor and report when important activity changes."
MCP Contract
Root endpoint:
https://mcp.hiveintelligence.xyz/mcpLocal development endpoint:
http://localhost:8080/mcpRoot MCP tools:
search_tools- 10 category listing tools, one per crypto domain
get_api_endpoint_schemainvoke_api_endpoint
Stateful Monitoring And B2B State
Hive's stateful monitor tools let authenticated agents store durable crypto intelligence intent in Hive instead of relying on chat memory. Direct users get one default state subject per Hive account. B2B partners can use one Hive API key from a trusted backend adapter while isolating downstream customers by signed tenant/end-user subject headers.
The stateful surface includes monitor CRUD, stored run reads, observations,
alerts, latest snapshots, memory facts, generated reports, and B2B subject admin
tools. The scheduled worker runs wallet, token, protocol, market,
prediction-market, watchlist digest, token discovery risk, and risk watch
workflows. See
docs/DOCUMENTATION.md for the
full monitor, subject-signing, worker, table, and smoke-test contract.
For partner products, use
docs/B2B_PARTNER_ADOPTION.md as the
implementation checklist.
TypeScript B2B adapters should use hive-mcp-client/b2b instead
of hand-building subject headers or raw monitor calls. If npm returns 404,
publish the client package with
docs/MCP_CLIENT_RELEASE.md before partners
depend on it:
import { createHiveB2BAdapter } from "hive-mcp-client/b2b";
const hive = await createHiveB2BAdapter({
apiKey: process.env.HIVE_API_KEY!,
subjectSigningSecret: process.env.HIVE_SUBJECT_SIGNING_SECRET!,
});
await hive.createWatchlistDigestMonitor(
{ tenantId: workspaceId, endUserId: userId },
{
name: "Daily portfolio brief",
target: { wallets, tokens },
cadence: "daily",
},
);Verify a B2B key and signed-subject isolation with:
curl https://mcp.hiveintelligence.xyz/api/v1/b2b/readiness \
-H "Authorization: Bearer $HIVE_API_KEY"HIVE_API_KEY="hive_live_..." \
HIVE_SUBJECT_SIGNING_SECRET="hive_subject_..." \
npm run smoke:b2b-partnerDiscovery resources:
hive://providershive://categorieshive://toolshive://toolsetshive://task-canarieshive://skillshive://status
Reusable prompts:
analyze_tokencompare_protocolsportfolio_audit
Category-scoped MCP endpoints remain available for clients that need direct tool lists:
/hive_market_data/mcp/hive_onchain_dex/mcp/hive_portfolio_wallet/mcp/hive_token_contract/mcp/hive_defi_protocol/mcp/hive_nft_analytics/mcp/hive_security_risk/mcp/hive_network_infrastructure/mcp/hive_search_discovery/mcp/hive_prediction_markets/mcp
Providers
| Provider | Coverage | Env var |
| --- | --- | --- |
| Alchemy | EVM wallet, token, NFT, transfer, simulation, gas, and RPC data | ALCHEMY_API_KEY |
| CoinGecko | Prices, OHLC, trending, news | COINGECKO_PRO_API_KEY |
| DeFiLlama | TVL, yields, fees, bridges | Free |
| CCXT | CEX data, funding rates, perpetuals | Free |
| GoPlus | Token, wallet, and dApp security | GOPLUS_APP_KEY + GOPLUS_APP_SECRET |
| Codex | DEX analytics and Polymarket prediction markets | CODEX_API_KEY |
| Helius | Solana RPC, DAS, priority fees, wallet history | HELIUS_API_KEY |
| Moralis | Wallet, token, NFT, PnL, DeFi positions | MORALIS_API_KEY |
| Tenderly | EVM simulation, tracing, gas estimation | TENDERLY_API_KEY |
Providers without configured keys remain discoverable and return classified
runtime status such as missing_key, plan_required, rate_limited,
degraded, or failing when execution is unavailable.
REST API
Use REST when your app does not speak MCP.
List tools:
curl -X GET "https://mcp.hiveintelligence.xyz/api/v1/tools?search=price&limit=20" \
-H "Authorization: Bearer $HIVE_API_KEY"Execute a tool:
curl -X POST https://mcp.hiveintelligence.xyz/api/v1/execute \
-H "Authorization: Bearer $HIVE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tool": "get_price",
"args": {
"ids": "bitcoin",
"vs_currencies": "usd"
}
}'Troubleshooting
| Symptom | What to check |
| --- | --- |
| API key required | Run hive auth login, pass --api-key, or set the hosted MCP Authorization: Bearer ... header. |
| Unsupported engine or install failure | Use Node.js 20 or newer. |
| Hosted MCP works in one client but not another | Confirm the client supports custom headers. Claude.ai custom connectors need OAuth-compatible auth, which Hive does not implement yet. |
| A provider tool returns missing_key | The tool is discoverable, but that provider needs an env var such as ALCHEMY_API_KEY, HELIUS_API_KEY, or MORALIS_API_KEY. |
| A provider returns rate_limited, degraded, or failing | Check hive status, hive doctor, or hive://status for runtime status and retry guidance. |
| npx install/cache errors | Retry with a clean cache: NPM_CONFIG_CACHE=$(mktemp -d) npx -y -p hive-intelligence@latest hive --help. |
Develop Locally
Install:
npm installRun:
npm run dev # stdio MCP
npm run dev:http # HTTP MCP and REST API on :8080Verify:
npm run checkFocused checks:
npm run build
npm run test:unit
npm run test:mcp-compliance
npm run verify:toolsets
npm run verify:agent-skills
npm run env:render:checkPackage Contents
The hive-intelligence npm package includes:
hive,hive-intelligence,hive-mcp, andhive-mcp-serverbinaries.- Built MCP server and CLI files in
build/. - Bundled Hive agent skills in
agent-skills/. - Local
stdioMCP runtime for desktop clients and self-hosting.
Contributor Context
Core implementation areas:
src/mcpServer.tsbuilds the MCP servers, tools, resources, prompts, and runtime instructions.src/server.tsruns Express, Streamable HTTP MCP, REST routes, auth, middleware, discovery descriptors, and shutdown.src/taskToolsets.tsdefines the workflow surface agents should prefer over raw endpoint browsing.src/cli.tsandsrc/cli/expose auth, setup, discovery, execution, diagnostics, config generation, aliases, and watch mode.agent-skills/ships agent-installable Hive skills.
Links
- Website: https://www.hiveintelligence.xyz
- Hosted MCP: https://mcp.hiveintelligence.xyz/mcp
- Public SDK and issues: https://github.com/hive-intel/hive-sdk
- Public tool catalog: https://mcp.hiveintelligence.xyz/api/v1/tools
- Install guides: https://www.hiveintelligence.xyz/install
- Quick start: https://www.hiveintelligence.xyz/quick-start
