
Cryptocompare MCP server
online · 100% uptimeCoinDesk Data (formerly CryptoCompare / CCData) MCP.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Cryptocompare yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cryptocompare tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Cryptocompare compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 87/100
- higher than 73% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 125 ms
- faster than 78% of 30,031 servers
Release history: 8 versions in the registry since 2026-05-19, latest 2026-10-31, typically one every 5 days.
Install Cryptocompare in Claude Code, Cursor or VS Code
claude mcp add --transport http cryptocompare https://gateway.pipeworx.io/cryptocompare/mcp
What the publisher says
From the Cryptocompare repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/cryptocompare
CoinDesk Data (formerly CryptoCompare / CCData) MCP — crypto prices, OHLC history, social stats, news.
Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.
The vendor renamed twice: developers.ccdata.io 301s to developers.coindesk.com, and min-api's own 401 body points callers there. The legacy data host min-api.cryptocompare.com still serves and is what this pack calls; data-api.coindesk.com is the current host.
Status 2026-08-21: the shared platform key is over quota. Every tool authenticates but returns the vendor body "You are over your rate limit please upgrade your account!", which this pack surfaces as {found:false, reason:"rate_limit", …} with a hint pointing at crypto, kraken and FRED. No plan or quota is quoted here because CoinDesk Data's pricing page no longer publishes one without an account — see .
Auth
- Platform: PLATFORMCRYPTOCOMPAREKEY. BYO: ?_apiKey=….
Tools
- price(fsym, tsyms, e?, extraParams?, sign?) — current price (one coin → many fiat)
- price_multi(fsyms, tsyms, e?, extraParams?, sign?) — current price (many → many)
- price_full(fsyms, tsyms, e?) — full snapshot (24h vol, etc.)
- histo_minute(fsym, tsym, limit?, aggregate?, toTs?, e?) — minute OHLC
- histo_hour(fsym, tsym, limit?, aggregate?, toTs?, e?) — hourly OHLC
- histo_day(fsym, tsym, limit?, aggregate?, toTs?, e?) — daily OHLC
- top_pairs(fsym, limit?) — top trading pairs
- topvolumefull(tsym, limit?, page?) — top by volume
- topmarketcap(limit?, tsym?, page?) — top by market cap
- news(lang?, sortOrder?, lTs?, feeds?, categories?, excludeCategories?) — news feed
- news_categories() — news categories
- news_feeds() — news feeds
Data sources
- API: https://min-api.cryptocompare.com (legacy host, still live; current host is https://data-api.coindesk.com)
- Docs + keys:
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"cryptocompare": {
"url": "https://gateway.pipeworx.io/cryptocompare/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/cryptocompare/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/cryptocompare_price \
-H 'Content-Type: application/json' \
-d '{"fsym":"BTC","tsyms":"USD,EUR"}'Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Cryptocompare: common questions
- Is Cryptocompare MCP server safe?
- Yes, by our scan: it is graded A (87/100). Read the Cryptocompare safety report
- How do I install Cryptocompare?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Cryptocompare need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Cryptocompare maintained?
- The last commit was 40 days ago (2026-09-24). The latest release is v0.2.1.
- Is Cryptocompare up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Cryptocompare compare with other MCP servers?
- safety score 87/100 (higher than 73% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 125 ms (faster than 78% of 30,031 servers). Full comparison.