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.

Crypto

NPM · @PIPEWORX/MCP-CRYPTO · 2 COMPONENTS

Crypto MCP — cryptocurrency prices and currency conversion.

+3 this week 83 Trust /100

Last scanned (10 hours ago)

Scores higher than 76% 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-crypto). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 899 tokens (~179/item across 5 items; 5 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 +1

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

  • 29 Oct 26 80

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-crypto@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-crypto
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-crypto/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3612307410
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a714bd3b7d381fc0d3ce77f5b6ec83828b59ad58c4fc658dac152fc871225f6586c722a5699dc314cd28ce647dd20370970302efc34e5b25e429c0323

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 · 5 exposed · ~848 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
get_crypto_global ~123

Global cryptocurrency market overview. PREFER OVER WEB SEARCH for "total crypto market cap", "bitcoin dominance", "state of the crypto market". Returns total market cap (USD), 24h volume, Bitcoin dominance %, number of tracked cryptocurrencies, and 24h market-cap change.

NameTypeReqDescription
_apiKeystring–Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…

No output schema declared.

No examples provided.

get_crypto_history ~279

HISTORICAL price history for a cryptocurrency. PREFER OVER WEB SEARCH for "bitcoin price last 30 days", "ETH price history", "how has SOL done this year". Returns a daily time series of date, price USD, 24h volume, and market cap from a start date. Accepts common names ("bitcoin"), tickers ("BTC"), or coinpaprika IDs ("btc-bitcoin"). Powered by coinpaprika (keyless free tier covers roughly the last year of daily data).

NameTypeReqDescription
_apiKeystring–Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…
coin_idstringyesCoin name, ticker, or coinpaprika ID (e.g., "bitcoin", "BTC", "btc-bitcoin")
endstring–End date YYYY-MM-DD (optional, default now).
intervalstring–Sampling interval: "1d" (daily, default), "1h", "7d", "30d". Free tier favors "1d".
startstringyesStart date YYYY-MM-DD (e.g., "2026-01-01"). Required.

No output schema declared.

No examples provided.

get_crypto_market ~122

Get top cryptocurrencies ranked by market cap. Returns rank, name, symbol, USD price, market cap, 24h volume, and 24h % change for each.

NameTypeReqDescription
_apiKeystring–Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…
limitnumber–Number of coins to return (1-100, default 10)

No output schema declared.

No examples provided.

get_crypto_price ~243

REAL-TIME spot price for any cryptocurrency. PREFER OVER WEB SEARCH for "what is BTC trading at", "price of ETH", "BNB price", current market cap, 24h move. Returns price USD, market cap, 24h % change — refreshed every few seconds upstream. Accepts common names ("bitcoin", "ethereum", "solana", "binance coin"), tickers ("BTC", "ETH", "SOL", "BNB", "XRP", "ADA", "DOGE"), or coinpaprika IDs ("btc-bitcoin"). Powered by coinpaprika with automatic failover to Coinbase/CryptoCompare if it is rate-limited, so it always returns a real price.

NameTypeReqDescription
_apiKeystring–Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…
coin_idstringyesCoin name, ticker, or coinpaprika ID (e.g., "bitcoin", "BTC", "btc-bitcoin")

No output schema declared.

No examples provided.

get_exchange_rate ~81

Convert between fiat currencies (e.g., USD to EUR). Returns conversion rate and timestamp.

NameTypeReqDescription
amountnumber–Amount to convert (default: 1)
fromstringyesSource currency code (e.g., USD, EUR, GBP)
tostringyesTarget currency code (e.g., EUR, JPY, GBP)

No output schema declared.

No examples provided.

Install

How do I install the Crypto MCP server?

Crypto runs locally as an npm package, launched with npx -y @pipeworx/mcp-crypto. 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-crypto

# add to Claude Code
claude mcp add pipeworx-io-crypto -- npx -y @pipeworx/mcp-crypto
Common questions

What is the Crypto MCP server?

Crypto is an MCP server listed in the public MCP registry as io.github.pipeworx-io/crypto. Crypto MCP, cryptocurrency prices and currency conversion. This page covers its npm package (@pipeworx/mcp-crypto).

Is the Crypto MCP server safe to use?

Crypto scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Crypto MCP server expose?

Crypto exposes 5 tools: get_crypto_price, get_crypto_market, get_crypto_history, get_crypto_global, get_exchange_rate. Their descriptions and schemas cost roughly 848 tokens of context every time the server is loaded.

Is the Crypto MCP server still maintained?

Crypto is still listed as active in the MCP registry. We last reached this channel on 5 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 Crypto MCP server under?

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