# Cryptocompare (npm · @pipeworx/mcp-cryptocompare)

CoinDesk Data (formerly CryptoCompare / CCData) MCP.

- Trust score: 87/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 86/100, [markdown](https://verifymcp.io/servers/pipeworx-io-cryptocompare/cryptocompare-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-cryptocompare/cryptocompare-mcp)
- npm · `@pipeworx/mcp-cryptocompare`: 87/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-cryptocompare/pipeworx-mcp-cryptocompare.md), [page](https://verifymcp.io/servers/pipeworx-io-cryptocompare/pipeworx-mcp-cryptocompare)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-cryptocompare`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cryptocompare).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2354 tokens (~156/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Cryptocompare MCP server?

Cryptocompare runs locally as an npm package, launched with npx -y @pipeworx/mcp-cryptocompare. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-cryptocompare -- npx -y @pipeworx/mcp-cryptocompare
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-cryptocompare": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cryptocompare"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-cryptocompare": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cryptocompare"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-cryptocompare -- npx -y @pipeworx/mcp-cryptocompare
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-cryptocompare": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-cryptocompare"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-cryptocompare --command npx --arg -y --arg @pipeworx/mcp-cryptocompare
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-cryptocompare:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-cryptocompare"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-cryptocompare": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-cryptocompare"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-cryptocompare -t stdio -c npx -a -y @pipeworx/mcp-cryptocompare
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-cryptocompare": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cryptocompare"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (15)

### `price` (~164 tokens)

Current crypto spot price from CoinDesk Data (formerly CryptoCompare): one coin (fsym) quoted in many fiat or crypto symbols (tsyms), aggregated across major exchanges. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `e` (string)
- `extraParams` (string)
- `fsym` (string, required)
- `sign` (boolean)
- `tsyms` (string, required)

### `price_multi` (~167 tokens)

Current crypto spot prices from CoinDesk Data (formerly CryptoCompare) for many coins at once (fsyms) quoted in many symbols (tsyms), aggregated across major exchanges. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `e` (string)
- `extraParams` (string)
- `fsyms` (string, required)
- `sign` (boolean)
- `tsyms` (string, required)

### `price_full` (~158 tokens)

Fetch full market snapshot for multiple crypto pairs (fsyms → tsyms): price, 24h change/%, volume, market cap, open/high/low from CoinDesk Data (formerly CryptoCompare). Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `e` (string)
- `fsyms` (string, required)
- `tsyms` (string, required)

### `histo_minute` (~185 tokens)

Minute-granularity historical OHLC + volume for a crypto pair (BTC/USD, ETH/USDT, etc.) across major exchanges. Use for short-timeframe charting, intraday backtests, and tick-level analysis. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `aggregate` (number)
- `e` (string)
- `fsym` (string, required)
- `limit` (number)
- `toTs` (number)
- `tsym` (string, required)

### `histo_hour` (~179 tokens)

Hourly historical OHLC + volume for a crypto pair (BTC/USD, ETH/USDT, etc.). Use for medium-timeframe crypto charting, swing-trading analysis, multi-day backtests. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `aggregate` (number)
- `e` (string)
- `fsym` (string, required)
- `limit` (number)
- `toTs` (number)
- `tsym` (string, required)

### `histo_day` (~177 tokens)

Daily historical OHLC + volume for a crypto pair (BTC/USD, ETH/USDT, etc.). Use for long-horizon crypto charting, multi-year backtests, and macro analysis. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `aggregate` (number)
- `e` (string)
- `fsym` (string, required)
- `limit` (number)
- `toTs` (number)
- `tsym` (string, required)

### `top_pairs` (~143 tokens)

Return the top trading pairs for a base coin (fsym) by 24h volume on CoinDesk Data (formerly CryptoCompare), with exchange and volume data for each pair. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `fsym` (string, required)
- `limit` (number)

### `top_volume_full` (~143 tokens)

Return the top cryptocurrencies ranked by 24h total volume denominated in a quote symbol (tsym); paginates with page parameter. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `limit` (number)
- `page` (number)
- `tsym` (string, required)

### `top_market_cap` (~140 tokens)

Return the top cryptocurrencies ranked by market capitalization denominated in a quote symbol (tsym); paginates with page parameter. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `limit` (number)
- `page` (number)
- `tsym` (string)

### `news` (~197 tokens)

CoinDesk Data (formerly CryptoCompare) aggregated crypto news feed: Bitcoin/Ethereum/altcoin headlines, exchange announcements, regulatory updates, market analysis. Filter by category (BTC, ETH, Trading, Regulation) or feed. Requires your own CoinDesk Data API key — for crypto news without one, use the `crypto-feeds` pack instead.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `categories` (string)
- `excludeCategories` (string)
- `feeds` (string)
- `lTs` (number)
- `lang` (string)
- `sortOrder` (string)

### `news_categories` (~129 tokens)

List crypto news category tags available for filtering the news feed (BTC, ETH, Trading, Regulation, Mining, etc.). Use as a directory before calling news() with a category filter. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…

### `news_feeds` (~134 tokens)

List crypto news source publishers CoinDesk Data (formerly CryptoCompare) aggregates (CoinDesk, CoinTelegraph, etc.) with feed IDs and metadata. Use as a directory before filtering news() by source. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…

### `social_stats` (~132 tokens)

Fetch social media stats for a coin by CoinDesk Data (formerly CryptoCompare) coinId: Twitter followers, Reddit subscribers, Facebook likes, GitHub activity. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…
- `coinId` (number, required)

### `all_coins` (~127 tokens)

Return the full CoinDesk Data (formerly CryptoCompare) coin list with symbol, name, CoinId, algorithm, proof type, and asset type for every tracked cryptocurrency. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…

### `all_exchanges` (~124 tokens)

Return metadata for all crypto exchanges tracked by CoinDesk Data (formerly CryptoCompare): name, country, grade, trading pairs, fee, and website URL. Requires your own CoinDesk Data API key.

Input parameters:

- `_apiKey` (string, required): Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (ge…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-cryptocompare/pipeworx-mcp-cryptocompare#diagnostics

## Score history

- 2026-11-22: 87
- 2026-11-21: 86
- 2026-11-20: 86
- 2026-11-19: 85
- 2026-11-18: 85
- 2026-11-17: 84
- 2026-11-16: 84
- 2026-11-15: 83
- 2026-11-14: 83
- 2026-11-13: 82
- 2026-11-12: 82
- 2026-11-11: 82
- 2026-11-10: 81
- 2026-11-09: 81
- 2026-11-08: 80
- 2026-11-07: 80
- 2026-11-06: 79
- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 61
- 2026-10-30: 76
- 2026-10-29: 75

## Common questions

### What is the Cryptocompare MCP server?

Cryptocompare is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cryptocompare. CoinDesk Data (formerly CryptoCompare / CCData) MCP. This page covers its npm package (@pipeworx/mcp-cryptocompare).

### Is the Cryptocompare MCP server safe to use?

Cryptocompare scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Cryptocompare MCP server expose?

Cryptocompare exposes 15 tools: price, price_multi, price_full, histo_minute, histo_hour, and 10 more. Their descriptions and schemas cost roughly 2,299 tokens of context every time the server is loaded.

### Is the Cryptocompare MCP server still maintained?

Cryptocompare is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Cryptocompare MCP server under?

Cryptocompare declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Cryptocompare MCP server?

VerifyMCP ran 16 checks on Cryptocompare, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-cryptocompare
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-cryptocompare
- Repository: https://github.com/pipeworx-io/mcp-cryptocompare
- Website: https://pipeworx.io/packs/cryptocompare
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-cryptocompare/pipeworx-mcp-cryptocompare.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-cryptocompare/pipeworx-mcp-cryptocompare/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-cryptocompare/pipeworx-mcp-cryptocompare.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-cryptocompare/pipeworx-mcp-cryptocompare
