# hive-intel/hive-crypto-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/hive-intel/hive-crypto-mcp  
**GitHub Stars:** 20  
**npm Downloads (last month):** 2054  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hive-intel-hive-crypto-mcp

## Description
Hive Intelligence: Ultimate cryptocurrency MCP for AI assistants with unified access to crypto, DeFi, and Web3 analytics

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "hive-crypto-mcp": {
    "command": "npx",
    "args": ["-y","-p","hive-intelligence@latest","hive"]
  }
}
```

## Documentation

## What hive-intel/hive-crypto-mcp MCP server does

hive-intel/hive-crypto-mcp MCP server gives AI clients a single interface for crypto and Web3 data. Its coverage includes live market information, wallet and portfolio activity, DeFi metrics, token and contract security, decentralized exchange flows, NFTs, and blockchain network data.

The service aggregates eleven named upstream sources plus Open Data Fetch. These include Alchemy, CoinGecko, DeFiLlama, Moralis, GoPlus, Helius, Tenderly, CCXT, Hyperliquid, RWA Perps, and Hive Archive. Coverage varies by provider and includes areas such as prices and OHLCV, TVL and yields, EVM and Solana wallets, token risk, simulations, exchange order books, derivatives, and network activity.

## How it works

The hosted deployment is available at `https://mcp.hiveintelligence.xyz/mcp` over Streamable HTTP. Clients can connect through OAuth after hosted authorization is enabled, while headless automation can send a Hive API key as a bearer token. Anonymous use is available for up to 25 material calls per IP per day; discovery, schema lookup, and validation calls are free.

A local installation runs the published `hive-intelligence` package as a stdio MCP process. Local mode does not use the hosted `HIVE_API_KEY`; instead, it can call upstream services directly when their keys are configured. Providers without credentials remain discoverable and report a classified `missing_key` runtime status.

Material executions include provider information, Hive retrieval time, first-observation or original cache time, cache age, fallback state, runtime status, and a unique receipt. This metadata helps an agent distinguish current, cached, or fallback results.

## Setup and configuration

For hosted use, add the endpoint to an MCP client using its remote HTTP configuration. The README provides configurations for Claude Code, Cursor, VS Code, Claude Desktop, Windsurf, and Gemini CLI. Interactive clients should begin with URL-only OAuth discovery. Headless clients can store a key securely and send `Authorization: Bearer $HIVE_API_KEY`; the legacy `x-api-key` header is also supported.

For local stdio use, configure `npx -y -p hive-intelligence@latest hive` as the command. The supported provider variables shown in the setup example are `COINGECKO_DEMO_API_KEY`, `ALCHEMY_API_KEY`, `HELIUS_API_KEY`, and `MORALIS_API_KEY`. All are described as optional, so available coverage depends on the credentials supplied.

## Tools and capabilities

The hive-intel/hive-crypto-mcp MCP server exposes one normalized tool surface rather than requiring separate client connections for each provider. Supported capability areas include:

- Market prices, OHLCV, exchanges, and tokenized real-world asset markets
- EVM and Solana wallet, token, NFT, transfer, and portfolio data
- DeFi TVL, yield pools, protocol metrics, bridges, and treasuries
- Token security, honeypot checks, contract risk, and malicious-address reputation
- DEX, centralized exchange, derivatives, funding, leverage, and borrow-rate data
- EVM simulation, gas, traces, contract decoding, and transaction analysis
- Solana RPC, compressed NFT, parsed-event, and priority-fee data

## Limitations and notes

Hosted anonymous access is quota-limited, and authenticated usage is governed by the selected plan's rate limits and credits. Local mode requires the relevant upstream credentials for provider-backed features, although keyless providers can still be used. API keys should remain in secret storage and must not be placed in install links, shared configurations, screenshots, repositories, or client-side code. The local package communicates over JSON-RPC stdio; it is not an interactive terminal command.

_Full upstream README: https://allmcps.com/mcp/hive-intel-hive-crypto-mcp/readme_