# Cryptocompare [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pipeworx-io/mcp-cryptocompare  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/cryptocompare

## Description
CryptoCompare prices, OHLC history, social stats, news, exchanges.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "cryptocompare": {
    "command": "npx",
    "args": ["-y","cryptocompare"]
  }
}
```

## Documentation & README

# @pipeworx/cryptocompare

[CoinDesk Data](https://developers.coindesk.com/) (formerly CryptoCompare / CCData) MCP —
crypto prices, OHLC history, social stats, news.

Part of [Pipeworx](https://pipeworx.io) — 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/>.

## Auth

- Platform: `PLATFORM_CRYPTOCOMPARE_KEY`. 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
- `top_volume_full(tsym, limit?, page?)` — top by volume
- `top_market_cap(limit?, tsym?, page?)` — top by market cap
- `news(lang?, sortOrder?, lTs?, feeds?, categories?, excludeCategories?)` — news feed
- `news_categories()` — news categories
- `news_feeds()` — news feeds
- `social_stats(coinId)` — social stats by coin id
- `all_coins()` — full coin list
- `all_exchanges()` — exchange list

## Data sources

- API: `https://min-api.cryptocompare.com` (legacy host, still live; current host is `https://data-api.coindesk.com`)
- Docs + keys: <https://developers.coindesk.com/>

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "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** — `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:

```json
{
  "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.

## Using with ask_pipeworx

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.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT