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.

47620 Solana Data API

NPM · 47620-SOLANA-MCP · 2 COMPONENTS

x402 pay-per-call Solana data + crypto market + JWT/unit utils for AI agents.

0 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% 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 Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @solana/web3.js > jayson > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 65 of 213 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 54 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1685 tokens (~64/item across 26 items; 26 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "should_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 26 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 (15)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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.

  • 21 Nov 26 +1

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

  • 20 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +1

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

  • 10 Nov 26 +1

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

  • 8 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.

  • 6 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.

  • 4 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.

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 21 Nov 2026 · Analysed npm/47620-solana-mcp@1.1.0

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 5 findings
ID CVE Severity Vector Fix available
GHSA-3gc7-fjrx-p6mg CVE-2025-3194 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hqr4-qq8f-hg3x CVE-2026-104182 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mjw6-4jj6-33hc CVE-2026-104183 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 213 packages
Packages resolved 213
Deprecated 1
Stale 64
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 26 exposed · ~1,685 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
crypto_deep ~68

Full decision pack in ONE call: spot + 24h stats + last candle + technical indicators (RSI/EMA/SMA) + funding/open interest + order-book spread/imbalance ($0.02 USDC).

NameTypeReqDescription
intervalstring––
symbolstringyes–

No output schema declared.

No examples provided.

crypto_derivatives ~47

Perpetual-futures context for a coin: funding rate, mark vs index price, next funding time, open interest ($0.005 USDC).

NameTypeReqDescription
symbolstringyes–

No output schema declared.

No examples provided.

crypto_indicators ~88

Technical indicator snapshot for a coin: RSI(14) with overbought/oversold signal, EMA(20/50), SMA(20/50/200). Query: interval, limit. The exact 'rsi ema' analysis agents ask for ($0.004 USDC).

NameTypeReqDescription
intervalstring––
limitnumber––
symbolstringyes–

No output schema declared.

No examples provided.

crypto_ohlcv ~120

OHLCV candle history for a coin. Query: interval (1m,5m,15m,1h,4h,1d) and limit (<=500). Returns [openTime,open,high,low,close,volume] rows ($0.003 USDC).

NameTypeReqDescription
intervalstring–1m|5m|15m|1h|4h|1d (default 1h)
limitnumber–<=500 (default 100)
symbolstringyes–

No output schema declared.

No examples provided.

crypto_orderbook ~61

Top-of-book for a coin: best bid/ask, mid, spread (+bps), depth and book imbalance. Query: limit (5-100). $0.005 USDC.

NameTypeReqDescription
limitnumber––
symbolstringyes–

No output schema declared.

No examples provided.

crypto_price ~79

Live spot price in USD (+24h change/high/low/volume) for a coin: btc, eth, sol, bnb, xrp, ada, doge, avax, link, matic, arb, op. Cheapest call ($0.002 USDC).

NameTypeReqDescription
symbolstringyesCoin symbol, e.g. btc

No output schema declared.

No examples provided.

jwt_decode ~58

Decode a JWT and extract claims (sub/iss/aud/exp+expired/iat/nbf, alg, kid). Decode-only, signature NOT verified ($0.002 USDC).

NameTypeReqDescription
tokenstringyesThe JWT compact string

No output schema declared.

No examples provided.

mcp_trust_check ~74

Verify BEFORE connecting: given an MCP server URL, check reachability, handshake, HTTPS, advertised tools, risky capabilities (shell/file/exec) and prompt-injection exposure. Returns safe|review|avoid. $0.02 USDC.

NameTypeReqDescription
targetstringyesMCP server URL (https://…)

No output schema declared.

No examples provided.

multichain_balance ~57

Native + stablecoin balances for an address on any chain. chain=solana|base|polygon. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
addressstringyesWallet address
chainstringyes–

No output schema declared.

No examples provided.

multichain_health ~45

Network health on any chain. chain=solana|base|polygon. Pay-per-call ($0.001 USDC).

NameTypeReqDescription
chainstringyesChain to query

No output schema declared.

No examples provided.

multichain_token ~79

Live price, liquidity, 24h volume + DEX pairs for a token on any chain (SPL mint or ERC-20). chain=solana|base|polygon. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
chainstringyes–
tokenstringyesSPL mint or ERC-20 contract address

No output schema declared.

No examples provided.

multichain_trending ~50

Trending DEX pairs by 24h volume on any chain. chain=solana|base|polygon. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
chainstringyes–

No output schema declared.

No examples provided.

multichain_trust_check ~73

BEFORE paying a payee: a multichain safe|review|avoid verdict from re-verifiable on-chain facts (Solana, Base, Polygon). Pay-per-call ($0.02 USDC).

NameTypeReqDescription
chainstring––
targetstringyesPayee address or ENS/domain

No output schema declared.

No examples provided.

multichain_tx ~70

Transaction status + transfer summary on any chain (Solana signature or EVM 0x hash). chain=solana|base|polygon. Pay-per-call ($0.003 USDC).

NameTypeReqDescription
chainstringyes–
hashstringyesTransaction signature or 0x hash

No output schema declared.

No examples provided.

qr_generate ~80

Generate a QR code for any text/URL as inline SVG + base64 data URI. Query: text (required), size, margin. Pure CPU ($0.002 USDC).

NameTypeReqDescription
marginnumber–quiet-zone modules (default 4)
sizenumber–px per module (default 6)
textstringyes–

No output schema declared.

No examples provided.

sha256_fingerprint ~58

SHA-256 fingerprint of a string: full hex, colon-hex (SSH-style), short 16-char id, and base64. Deterministic, CPU-only ($0.001 USDC).

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

should_pay ~54

Pay-vs-do-not-pay decision for a payee on Base or Polygon. chain=base|polygon. Pay-per-call ($0.02 USDC).

NameTypeReqDescription
addressstringyes–
chainstringyes–

No output schema declared.

No examples provided.

solana_account ~50

Native SOL balance plus every SPL token balance (incl. USDC) for a Solana address. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
addressstringyesSolana wallet address

No output schema declared.

No examples provided.

solana_health ~34

Solana network health: current slot, epoch, and SOL/USD price. Pay-per-call ($0.001 USDC).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

solana_token ~51

Live price, liquidity, 24h volume and DEX pairs for any Solana SPL token mint. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
mintstringyesSPL token mint address

No output schema declared.

No examples provided.

solana_trending ~41

Live trending / new Solana DEX pairs by 24h volume. A fresh feed for agents. Pay-per-call ($0.005 USDC).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

solana_tx ~46

Status, slot, fee, block time and transfer summary for a Solana transaction signature. Pay-per-call ($0.003 USDC).

NameTypeReqDescription
signaturestringyesTransaction signature

No output schema declared.

No examples provided.

unit_convert ~93

Convert a value between units: length (m/km/mi/ft/in/yd/nmi + Russian verst/sazhen/arshin/vershok), mass (g/kg/lb/oz + pood/funt/zolotnik), area, temperature (C/F/K). $0.001 USDC.

NameTypeReqDescription
fromstringyes–
tostringyes–
valuenumberyes–

No output schema declared.

No examples provided.

unix_timestamp ~90

Convert between unix epoch and human time. value=<seconds|ms|ISO>; auto-detects units. Returns epoch s+ms, ISO-8601 UTC, and target-tz time (?tz=). $0.001 USDC.

NameTypeReqDescription
tzstring–IANA timezone, e.g. America/Santiago
valuestringyesunix seconds, ms, or ISO string

No output schema declared.

No examples provided.

x402_ecosystem_networks ~50

Network/asset histogram of the live x402 ecosystem (Base, Solana, Arbitrum, Polygon, …), with per-network service counts. $0.005 USDC.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402_ecosystem_stats ~69

LIVE, sourced x402 adoption stats: how many pay-per-call services are indexed, on which networks/assets/categories, and at what USD price points (min/median/mean/max). Every figure carries its source URL + fetchedAt; nothing fabricated. $0.01 USDC.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the 47620 Solana Data API MCP server?

47620 Solana Data API runs locally as an npm package, launched with npx -y 47620-solana-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 · 47620-solana-mcp

# add to Claude Code
claude mcp add xyz-47620-solana-data -- npx -y 47620-solana-mcp
Common questions

What is the 47620 Solana Data API MCP server?

47620 Solana Data API is an MCP server listed in the public MCP registry as xyz.47620/solana-data. x402 pay-per-call Solana data + crypto market + JWT/unit utils for AI agents. This page covers its npm package (47620-solana-mcp).

Is the 47620 Solana Data API MCP server safe to use?

47620 Solana Data API scores 73 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 21 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 47620 Solana Data API MCP server expose?

47620 Solana Data API exposes 26 tools: solana_health, solana_token, solana_account, solana_tx, solana_trending, and 21 more. Their descriptions and schemas cost roughly 1,685 tokens of context every time the server is loaded.

Is the 47620 Solana Data API MCP server still maintained?

47620 Solana Data API is still listed as active in the MCP registry. We last reached this channel on 21 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 47620 Solana Data API MCP server under?

47620 Solana Data API 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 47620 Solana Data API MCP server?

VerifyMCP ran 15 checks on 47620 Solana Data API, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about 47620 Solana Data API: Security disclosure. 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.