Enables AI assistants to access real-time on-chain crypto analytics, whale tracking, and market metrics through natural language queries. It provides access to over 245 endpoints for comprehensive data analysis of assets like Bitcoin, Ethereum, and stablecoins
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Version 0.2.0 declares 1 executable entrypoint.
npm install --save-exact cryptoquant-mcp@0.2.0npx -y -p cryptoquant-mcp@0.2.0 cryptoquant-mcp{
"mcpServers": {
"cryptoquant-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"cryptoquant-mcp@0.2.0",
"cryptoquant-mcp"
]
}
}
}| Canonical slug | cryptoquant-mcp-server-1974e00a | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:cryptoquant-mcp | Repository | CryptoQuantOfficial/cryptoquant-mcp |
| First published | — | Latest release | — |
| Last security verification | Aug 18, 2026 | Classification confidence | 90% |
| Publication | Published | Official distribution | Yes |
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | cryptoquant-mcp | 0.2.0 | 1 | Repository |
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npmcryptoquant-mcp | 0.2.0Current | Sep 5, 2026 | 7 toolsSucceeded · 0 resources · 0 prompts | Verified clean |
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
| Provenance | artifact_hash_verified | Signature | — |
|---|---|---|---|
| MCP SDK | @modelcontextprotocol/sdk | Artifact SHA-256 | 29607589a22f9a75b3b7887c756e4a50dc0a60ee858e86dcda488aee295001b4 |
| Scanner | mcp-proof-engine 0.1.0 | Scan completed | Aug 18, 2026 |
| Security rating | 33 / 100 | Methodology | version-rating-1.0 |
[ "cryptoquant-mcp" ]
| Tool | Category | Annotations | Risk |
|---|---|---|---|
describe_metricGet detailed description for a specific metric. Use only when user asks 'what is X?' or metric is unfamiliar. Returns thresholds, interpretation guidance, and category info.Input schema{
"type": "object",
"properties": {
"metric_id": {
"type": "string",
"description": "The metric ID to describe (e.g., 'mvrv', 'sopr', 'netflow')"
}
},
"required": [
"metric_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
discover_endpointsDiscover available API endpoints for a specific asset and category. Call initialize() first to get valid asset/category combinations. Returns endpoint paths and parameter options (e.g., window: ['day', 'hour']). Use returned paths with query_data().Input schema{
"type": "object",
"properties": {
"asset": {
"type": "string",
"enum": [
"btc",
"eth",
"alt",
"stablecoin",
"erc20",
"trx",
"xrp"
],
"description": "Asset to discover endpoints for. Omit for all assets."
},
"category": {
"type": "string",
"description": "Category filter (e.g., market-data, exchange-flows, network-data, miner-flows, etc.)"
},
"query": {
"type": "string",
"description": "Search term to filter endpoints by path or metric name"
},
"include_restricted": {
"type": "boolean",
"default": false,
"description": "Include endpoints not available on your current plan"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
get_endpoint_infoGet detailed information about a specific API endpoint including available parameter values.Input schema{
"type": "object",
"properties": {
"endpoint": {
"type": "string",
"description": "API endpoint path to get information about"
}
},
"required": [
"endpoint"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
initializeInitialize CryptoQuant session. MUST be called first before any other CryptoQuant tools. Returns available assets (btc, eth, etc.), metric categories per asset (e.g., market-indicator, network-indicator), and your plan. Use the returned asset_categories to know which discover_endpoints() calls are valid.Input schema{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "API key (optional if CRYPTOQUANT_API_KEY env var is set)"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
list_assetsList all supported assets (cryptocurrencies) with their available data categories.Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {}
} | — | — | |
query_dataQuery raw data from CryptoQuant API. Workflow: initialize() → discover_endpoints(asset, category) → query_data(endpoint, params). Use endpoint paths and parameter values from discover_endpoints response.Input schema{
"type": "object",
"properties": {
"endpoint": {
"type": "string",
"description": "API endpoint path (e.g., /v1/btc/market-data/mvrv)"
},
"params": {
"type": "object",
"properties": {
"window": {
"type": "string",
"description": "Time window granularity (hour, day, block, etc.)"
},
"limit": {
"type": "number",
"description": "Number of data points to return (max 1000)"
},
"from": {
"type": "string",
"description": "Start date (ISO 8601 format)"
},
"to": {
"type": "string",
"description": "End date (ISO 8601 format)"
},
"exchange": {
"type": "string",
"description": "Exchange filter (for exchange-specific data)"
},
"symbol": {
"type": "string",
"description": "Trading symbol (e.g., btc_usd, btc_usdt)"
},
"market": {
"type": "string",
"description": "Market type (spot, perpetual)"
},
"token": {
"type": "string",
"description": "Token filter (for alt/erc20 data)"
},
"miner": {
"type": "string",
"description": "Miner filter (for miner data)"
},
"type": {
"type": "string",
"description": "Entity type filter (e.g., exchange, entity, miner, bank)"
}
},
"additionalProperties": false,
"description": "Query parameters"
}
},
"required": [
"endpoint"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
reset_sessionClear session and optionally stored credentials. Use cases: (1) Switch accounts - clear_stored=true then initialize(), (2) API key expired - clear_stored=true then initialize(), (3) Refresh session - clear_stored=false. After clearing, call initialize() with your API key.Input schema{
"type": "object",
"properties": {
"clear_stored": {
"type": "boolean",
"description": "If true, also clears stored credentials from ~/.cryptoquant/credentials"
},
"clear_cache": {
"type": "boolean",
"description": "If true, also clears discovery cache (forces fresh API fetch on next initialize)"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — |
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Install the selected package version with: npm install --save-exact cryptoquant-mcp@0.2.0
CryptoQuant MCP Server exposed 7 tools during independent protocol observation, including describe_metric, discover_endpoints, get_endpoint_info, initialize, list_assets, query_data, reset_session.
Our scanner tested version 0.2.0 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.
Curated product and capability guides containing this catalog record.