
Connects Claude to CryptoCompare's cryptocurrency data API through Pipeworx's gateway infrastructure. You get six tools: current prices for single or multiple coins against fiat currencies, minute/hourly/daily OHLC candles for charting, and a news feed. Runs over streamable HTTP, so no local setup required. The ask_pipeworx wrapper lets you query in natural language instead of calling tools directly. Useful when you're building trading analysis, portfolio trackers, or need real-time crypto market data in your Claude workflows. Part of Pipeworx's larger catalog of 673+ data sources if you want to expand beyond cryptocurrency.
CoinDesk Data (formerly CryptoCompare / CCData) MCP — crypto prices, OHLC history, social stats, news.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ 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 https://developers.coindesk.com/pricing/.
PLATFORM_CRYPTOCOMPARE_KEY. BYO: ?_apiKey=….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 OHLChisto_hour(fsym, tsym, limit?, aggregate?, toTs?, e?) — hourly OHLChisto_day(fsym, tsym, limit?, aggregate?, toTs?, e?) — daily OHLCtop_pairs(fsym, limit?) — top trading pairstop_volume_full(tsym, limit?, page?) — top by volumetop_market_cap(limit?, tsym?, page?) — top by market capnews(lang?, sortOrder?, lTs?, feeds?, categories?, excludeCategories?) — news feednews_categories() — news categoriesnews_feeds() — news feedssocial_stats(coinId) — social stats by coin idall_coins() — full coin listall_exchanges() — exchange listhttps://min-api.cryptocompare.com (legacy host, still live; current host is https://data-api.coindesk.com)Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"cryptocompare": {
"url": "https://gateway.pipeworx.io/cryptocompare/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/cryptocompare/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, 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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Cryptocompare data" })
The gateway picks the right tool and fills the arguments automatically.
MIT