Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cryptocompare

NPM · @PIPEWORX/MCP-CRYPTOCOMPARE · 2 COMPONENTS

CoinDesk Data (formerly CryptoCompare / CCData) MCP.

+4 this week 87 Trust /100

Last scanned (21 hours ago)

Scores higher than 81% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cryptocompare). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 21 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Nov 26 +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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +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.

  • 7 Nov 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Analysed npm/@pipeworx/mcp-cryptocompare@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-cryptocompare
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-cryptocompare/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3612312305
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:b3731ab538111e9ede250fa12fad43b1e911d5dd192aff6a93556cffa1c71f4988ca39eba34dac199e305b1a4a68e3925aafaa52dd017477b558a65c4

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~2,299 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
all_coins ~127

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.

NameTypeReqDescription
_apiKeystringyesYour 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…

No output schema declared.

No examples provided.

all_exchanges ~124

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.

NameTypeReqDescription
_apiKeystringyesYour 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…

No output schema declared.

No examples provided.

histo_day ~177

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
aggregatenumber––
estring––
fsymstringyes–
limitnumber––
toTsnumber––
tsymstringyes–

No output schema declared.

No examples provided.

histo_hour ~179

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
aggregatenumber––
estring––
fsymstringyes–
limitnumber––
toTsnumber––
tsymstringyes–

No output schema declared.

No examples provided.

histo_minute ~185

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
aggregatenumber––
estring––
fsymstringyes–
limitnumber––
toTsnumber––
tsymstringyes–

No output schema declared.

No examples provided.

news ~197

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
categoriesstring––
excludeCategoriesstring––
feedsstring––
lTsnumber––
langstring––
sortOrderstring––

No output schema declared.

No examples provided.

news_categories ~129

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.

NameTypeReqDescription
_apiKeystringyesYour 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…

No output schema declared.

No examples provided.

news_feeds ~134

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.

NameTypeReqDescription
_apiKeystringyesYour 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…

No output schema declared.

No examples provided.

price ~164

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
estring––
extraParamsstring––
fsymstringyes–
signboolean––
tsymsstringyes–

No output schema declared.

No examples provided.

price_full ~158

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
estring––
fsymsstringyes–
tsymsstringyes–

No output schema declared.

No examples provided.

price_multi ~167

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
estring––
extraParamsstring––
fsymsstringyes–
signboolean––
tsymsstringyes–

No output schema declared.

No examples provided.

social_stats ~132

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
coinIdnumberyes–

No output schema declared.

No examples provided.

top_market_cap ~140

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
limitnumber––
pagenumber––
tsymstring––

No output schema declared.

No examples provided.

top_pairs ~143

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
fsymstringyes–
limitnumber––

No output schema declared.

No examples provided.

top_volume_full ~143

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.

NameTypeReqDescription
_apiKeystringyesYour 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…
limitnumber––
pagenumber––
tsymstringyes–

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-cryptocompare

# add to Claude Code
claude mcp add pipeworx-io-cryptocompare -- npx -y @pipeworx/mcp-cryptocompare
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.