CryptoQuant MCP Server

by cryptoquant Your server? Claim it

answering

CryptoQuant is answering right now. Last checked 12 min ago.

Query cryptocurrency on-chain data, OHLCV prices, market data, and Research & QuickTake insights.

Uptime history 47 days of history · worst day 90%

47 days agonow

98.9%

Uptime 24h

90 of 91 checks

—

Tools

hidden behind auth

510 ms

Response time

average over 24h

API key

Access

streamable-http

CryptoQuant does not always answer

Over the last week it answered 97.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp-server --transport http https://mcp.cryptoquant.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.cryptoquant.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp-server]
url = "https://mcp.cryptoquant.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.cryptoquant.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.cryptoquant.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.cryptoquant.com/mcp	streamable-http	needs key	298 ms	12 min ago

Alternatives to CryptoQuant

same job, measured the same way

Truss44 MCP Crypto Price

by smithery

Provide real-time cryptocurrency price data and market analysis.

answering

f1ow

by f1ow

Crypto market data & research MCP: price, derivatives, on-chain, sentiment, news, catalysts.

30 tools answering

CoinPaprika

by coinpaprika

Real-time crypto market data: prices, tickers, exchanges, OHLCV candles, and metadata.

31 tools answering

MCP Market Data

by cryptoapis-io

MCP server for cryptocurrency asset prices, exchange rates, and market metadata via Crypto APIs

63 installs/wk local only

Shumi

by shumi

Crypto market intelligence: prices, funding rates, narratives, regime, and delta-neutral research.

146 installs/wk 31 tools answering

crypto

by pipeworx-io

Crypto MCP — cryptocurrency prices and currency conversion

36 tools answering

Qoory Crypto Intelligence

by qoory-ai

One Data Plane for crypto research, with 42 live tools for markets, entities, news, and signals.

answering

TextToQuant Backtesting and Quant Research

by texttoquant

Backtest plain-English trading strategies on real market data: graded results, honesty flags.

answering

CryptoQuant — questions

Answers built from our own checks of this server.

Why is there no tool list for CryptoQuant?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.

Is CryptoQuant working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 510 ms. The bar chart above shows every period we have measured.

How do I connect CryptoQuant?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does CryptoQuant need an API key?

Yes. Every time we knock, CryptoQuant answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is CryptoQuant?

It answers our handshake in 510 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.