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 Market Data

NPM · CRYPTO-MARKET-DATA-MCP · 2 COMPONENTS

Live crypto market data and Hyperliquid wallet reports for AI agents, paid per call with x402.

+3 this week 69 Trust /100

Last scanned (3 hours ago)

Scores higher than 37% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 716 tokens (~55/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 28 Oct 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.

  • 26 Oct 26 +1

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

  • 25 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 24 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Schema quality: 50 → 55 ▼ functional
    • Tool coverage: 100% → 89% ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.1 → 0.1.3 functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 23 Oct 26 49

    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/crypto-market-data-mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 114 packages
Packages resolved 114
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~716 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
coin_snapshot ~45

Everything for one coin: price, derivatives, order book, liquidations, whales, news (USD 0.005).

NameTypeReqDescription
tokenstringyesOne ticker such as BTC

No output schema declared.

No examples provided.

create_watch ~120

Watch the crypto market for 24 hours: up to 10 conditions (price, % change, funding, open interest, liquidations, order book, Fear and Greed, whale orders, news impact) checked every minute; when one happens, a signed webhook goes to callback_url and it shows in watch_status. Level conditions fire when they turn true. Keep the returned secret (USD 0.02).

NameTypeReqDescription
callback_urlstring–https URL for the webhook (optional)
conditionsarrayyes–
labelstring––

No output schema declared.

No examples provided.

derivatives ~61

Funding rate, futures premium, open interest and long/short ratio per coin (USD 0.003).

NameTypeReqDescription
tokensstring–Comma-separated tickers such as BTC,ETH,SOL (up to 50). Empty means the top 50 coins.

No output schema declared.

No examples provided.

hyperliquid_wallet ~59

Enriched Hyperliquid wallet report: positions, liquidation distance, risk, PnL, volume (USD 0.01).

NameTypeReqDescription
addressstringyesHyperliquid wallet address, 0x followed by 40 hex characters

No output schema declared.

No examples provided.

liquidations ~51

Every Binance futures liquidation of the last hour by coin, plus the biggest (USD 0.003).

NameTypeReqDescription
limitinteger–How many rows
tokenstring–One ticker such as BTC

No output schema declared.

No examples provided.

news ~49

Top crypto stories now from 31 sources with impact and price reaction (USD 0.003).

NameTypeReqDescription
limitinteger–How many rows
tokenstring–One ticker such as BTC

No output schema declared.

No examples provided.

orderbook ~60

Bid-ask spread, order-book imbalance and buyer share per coin (USD 0.003).

NameTypeReqDescription
tokensstring–Comma-separated tickers such as BTC,ETH,SOL (up to 50). Empty means the top 50 coins.

No output schema declared.

No examples provided.

prices ~74

Live prices with 5m/1h/4h/24h change and 24h volume for the top 50 crypto coins (USD 0.003).

NameTypeReqDescription
tokensstring–Comma-separated tickers such as BTC,ETH,SOL (up to 50). Empty means the top 50 coins.

No output schema declared.

No examples provided.

sentiment ~36

Fear and Greed, trending coins, market breadth and mood (USD 0.003).

NameTypeReqDescription
limitinteger–How many rows

No output schema declared.

No examples provided.

service_info ~23

Free: what the service offers, prices, and session spending so far.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stop_watch ~41

Free: stop a watch before it expires.

NameTypeReqDescription
secretstringyessecret from create_watch
watch_idstringyeswatch_id from create_watch

No output schema declared.

No examples provided.

watch_status ~47

Free: a watch's status, conditions and its last 20 fires.

NameTypeReqDescription
secretstringyessecret from create_watch
watch_idstringyeswatch_id from create_watch

No output schema declared.

No examples provided.

whale_orders ~50

Biggest market orders of the last hour on Binance and Hyperliquid (USD 0.003).

NameTypeReqDescription
limitinteger–How many rows
tokenstring–One ticker such as BTC

No output schema declared.

No examples provided.

Install

How do I install the Crypto Market Data MCP server?

Crypto Market Data runs locally as an npm package, launched with npx -y crypto-market-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · crypto-market-data-mcp

# add to Claude Code
claude mcp add zaffy18-crypto-market-data -- npx -y crypto-market-data-mcp
Common questions

What is the Crypto Market Data MCP server?

Crypto Market Data is an MCP server listed in the public MCP registry as io.github.zaffy18/crypto-market-data. Live crypto market data and Hyperliquid wallet reports for AI agents, paid per call with x402. This page covers its npm package (crypto-market-data-mcp).

Is the Crypto Market Data MCP server safe to use?

Crypto Market Data scores 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Market Data MCP server expose?

Crypto Market Data exposes 13 tools: prices, derivatives, orderbook, liquidations, whale_orders, and 8 more. Their descriptions and schemas cost roughly 716 tokens of context every time the server is loaded.

Is the Crypto Market Data MCP server still maintained?

Crypto Market Data 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 Market Data MCP server under?

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