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 Multichain Data API — onchain, crypto, utilities, x402 stats

REMOTE · 47620.XYZ · SCANNED SEP 29

x402 pay-per-call: onchain data (Solana/Base/Polygon), crypto market, JWT/unit utils, x402 stats.

Available components

65 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2867 tokens (~84/item across 34 items; 34 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 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 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 34 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
Install

How do I install the 47620 Multichain Data API — onchain, crypto, utilities… MCP server?

47620 Multichain Data API — onchain, crypto, utilities… is a hosted endpoint at https://47620.xyz/mcp/multichain, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · 47620.xyz

# add to Claude Code
claude mcp add --transport http xyz-47620-multichain 'https://47620.xyz/mcp/multichain'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-47620-multichain": {
      "url": "https://47620.xyz/mcp/multichain"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-47620-multichain": {
      "type": "http",
      "url": "https://47620.xyz/mcp/multichain"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.xyz-47620-multichain]
url = "https://47620.xyz/mcp/multichain"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-47620-multichain": {
      "type": "remote",
      "url": "https://47620.xyz/mcp/multichain",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-47620-multichain --url 'https://47620.xyz/mcp/multichain' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-47620-multichain:
    url: "https://47620.xyz/mcp/multichain"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-47620-multichain": {
      "Transport": "http",
      "Url": "https://47620.xyz/mcp/multichain"
    }
  }
}
# add to Vellum
assistant mcp add xyz-47620-multichain -t streamable-http -u 'https://47620.xyz/mcp/multichain'
// mcp.json
{
  "mcpServers": {
    "xyz-47620-multichain": {
      "type": "http",
      "url": "https://47620.xyz/mcp/multichain"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 29 Sept 26 +1

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

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 64

    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 29 Sept 2026 · Probed https://47620.xyz/mcp/multichain

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=47620.xyz CN=YE2,O=Let's Encrypt,C=US 30 Aug 2026 28 Nov 2026 ECDSA 256 ECDSA-SHA384 6cc23e4e4e432d09e874d63ae8aeec1293c
SANs: 47620.xyz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of 47620.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
47620.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://47620.xyz/mcp/multichain Verified 200
http (plaintext) http://47620.xyz/mcp/multichain HTTPS enforced 308 https://47620.xyz/mcp/multichain
MCP tools · 34 exposed · ~2,867 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
account ~54

[Solana by default] 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.

balance ~102

Native + stablecoin balances for an address on a chosen chain. Paths: solana -> /x/solana/account/:address, base -> /x/base-fac/balance/:address, polygon -> /x/polygon-fac/balance/:address. Pay-per-call from $0.002 USDC.

NameTypeReqDescription
addressstringyesAddress (base58 on Solana, 0x... on EVM)
chainstringyesChain to query

No output schema declared.

No examples provided.

contract ~85

Whether an address is a contract + bytecode size + ERC-20 metadata (EVM). Paths: base -> /x/base-fac/contract/:address, polygon -> /x/polygon-fac/contract/:address. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
addressstringyesContract address (0x...)
chainstringyesEVM chain

No output schema declared.

No examples provided.

crypto_deep ~107

Full decision pack in ONE call for a crypto coin: spot + 24h stats, last candle, indicators (RSI/EMA/SMA), perpetual funding + open interest, and order-book spread/imbalance. -> /x/crypto/deep/:symbol. Pay-per-call ($0.02 USDC).

NameTypeReqDescription
intervalstring–Candle interval (default 1h)
symbolstringyesCoin ticker or name, e.g. btc, eth, sol

No output schema declared.

No examples provided.

crypto_derivatives ~83

Perpetual-futures context for a crypto coin: last funding rate (+%), mark vs index price, next funding time, and open interest (base + USD). -> /x/crypto/derivatives/:symbol. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
symbolstringyesCoin ticker or name, e.g. btc, eth, sol

No output schema declared.

No examples provided.

crypto_indicators ~108

Technical indicators for a crypto coin: RSI(14) with overbought/oversold signal, EMA(20), EMA(50), SMA(20/50/200). Optional interval (default 1h). -> /x/crypto/indicators/:symbol. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
intervalstring–Candle interval (default 1h)
symbolstringyesCoin ticker or name, e.g. btc, eth, sol

No output schema declared.

No examples provided.

crypto_ohlcv ~139

OHLCV candle history for a crypto coin: rows [openTime, open, high, low, close, volume]. Optional interval (1m,5m,15m,1h,4h,1d; default 1h) and limit (<=500). -> /x/crypto/ohlcv/:symbol. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
intervalstring–Candle interval (default 1h)
limitinteger–Number of candles (<=500, default 100)
symbolstringyesCoin ticker or name, e.g. btc, eth, sol

No output schema declared.

No examples provided.

crypto_orderbook ~105

Order-book top-of-book for a crypto coin: best bid/ask, mid price, spread (abs + bps), bid/ask depth and book imbalance (>0 = more bids). -> /x/crypto/orderbook/:symbol. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
limitinteger–Order-book levels (5-100, default 20)
symbolstringyesCoin ticker or name, e.g. btc, eth, sol

No output schema declared.

No examples provided.

crypto_price ~101

Live crypto spot price in USD for a coin (btc, eth, sol, bnb, xrp, ada, doge, avax, link, matic, arb, op): price + 24h change, high, low and quote volume. -> /x/crypto/price/:symbol. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
symbolstringyesCoin ticker or name, e.g. btc, eth, sol

No output schema declared.

No examples provided.

gas ~76

Current gas price + estimated transfer cost. Paths: base -> /x/base-fac/gas, polygon -> /x/polygon-fac/gas. (Solana uses fixed micro-lamport fees; use health for the fee context.) Pay-per-call ($0.005 USDC).

NameTypeReqDescription
chainstringyesEVM chain

No output schema declared.

No examples provided.

health ~69

Network health for a chosen chain. Paths: solana -> /x/solana/health, base -> /x/base-fac/health, polygon -> /x/polygon-fac/health. Pay-per-call from $0.001 USDC.

NameTypeReqDescription
chainstringyesChain to query

No output schema declared.

No examples provided.

jwt_decode ~76

Decode a JWT and extract its claims (subject, issuer, audience, expiration with expired flag, issued-at, not-before, algorithm, key id). Decode-only — signature NOT verified. -> /x/util/jwt-decode. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
tokenstringyesThe JWT string to decode

No output schema declared.

No examples provided.

qr_generate ~76

Generate a QR code for any text or URL and return it as inline SVG + base64 data URI. -> /x/util/qr. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
sizeinteger–Pixels per module (2-20, default 6)
textstringyesText or URL to encode

No output schema declared.

No examples provided.

risk_check ~115

BEFORE paying an address, get a 0-100 risk score with reasons and a proceed/review verdict, built from re-verifiable on-chain facts. chain -> /x/solana/risk/:address | /x/base-fac/risk/:address | /x/polygon-fac/risk/:address. Pay-per-call ($0.02 USDC).

NameTypeReqDescription
addressstringyesAddress to check before paying (0x... EVM or base58 Solana)
chainstringyesChain to query

No output schema declared.

No examples provided.

sha256_fingerprint ~62

Compute a SHA-256 fingerprint of a string: full hex, colon-separated, short 16-char id and base64. -> /x/util/fingerprint. Pay-per-call ($0.001 USDC).

NameTypeReqDescription
textstringyesText to fingerprint

No output schema declared.

No examples provided.

should_pay ~91

Pay-vs-do-not-pay decision for a payee, aggregating on-chain facts into a single verdict. chain -> /x/base-fac/should-pay/:address | /x/polygon-fac/should-pay/:address (EVM). Pay-per-call ($0.02 USDC).

NameTypeReqDescription
addressstringyesPayee address (0x...)
chainstringyesEVM chain

No output schema declared.

No examples provided.

snapshot ~86

Whole-network picture in ONE call: cluster health, slot/epoch (Solana) or chain status (EVM), native/USD price and top trending pairs. chain -> /x/solana/snapshot | /x/base-fac/snapshot | /x/polygon-fac/snapshot. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
chainstringyesChain to query

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_risk_check ~92

BEFORE sending SOL/USDC to any address, run this: returns account type (wallet vs program vs closed), balance, activity, and a 0-100 risk score with reasons and a proceed/review verdict. Use it to avoid paying a dead, wrong or program address. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
addressstringyesSolana address to check before paying

No output schema declared.

No examples provided.

solana_snapshot ~52

Whole-network picture in ONE call: cluster health, current slot, epoch progress, SOL/USD price AND top trending pairs. Cheaper than making 5 separate calls. Pay-per-call ($0.01 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_token_report ~72

Full token due-diligence in ONE call: live price, liquidity, 24h volume, DEX pairs, on-chain supply and mint authority. Use for token research instead of multiple lookups. Pay-per-call ($0.01 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.

token ~103

Live price, liquidity, 24h volume + DEX pairs for a token. Paths: solana -> /x/solana/token/:mint, base -> /x/base-fac/token/:address, polygon -> /x/polygon-fac/token/:address. Pay-per-call from $0.002 USDC.

NameTypeReqDescription
chainstringyesChain to query
idstringyesSPL mint (Solana) or ERC-20 address (EVM)

No output schema declared.

No examples provided.

token_report ~114

Full token due-diligence in ONE call: price, liquidity, 24h volume, DEX pairs, supply and (EVM) contract metadata. chain -> /x/solana/token-report/:token | /x/base-fac/token-report/:token | /x/polygon-fac/token-report/:token. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
chainstringyesChain to query
tokenstringyesSPL mint (Solana) or ERC-20 contract (EVM)

No output schema declared.

No examples provided.

trending ~71

Trending DEX pairs by 24h volume. Paths: solana -> /x/solana/trending, base -> /x/base-fac/trending, polygon -> /x/polygon-fac/trending. Pay-per-call ($0.02 USDC).

NameTypeReqDescription
chainstringyesChain to query

No output schema declared.

No examples provided.

trust_check ~99

BEFORE paying a wallet/payee, get a multichain safe|review|avoid verdict built only from re-verifiable on-chain facts (existence, activity, USDC settlements, contract code). Covers Solana, Base and Polygon. Pay-per-call ($0.02 USDC).

NameTypeReqDescription
chainstring–Optional; inferred if omitted
targetstringyesPayee address (0x... EVM or base58 Solana)

No output schema declared.

No examples provided.

tx ~99

Transaction status + transfer summary on a chosen chain. Paths: solana -> /x/solana/tx/:signature, base -> /x/base-fac/tx/:hash, polygon -> /x/polygon-fac/tx/:hash. Pay-per-call from $0.003 USDC.

NameTypeReqDescription
chainstringyesChain to query
idstringyesSignature (Solana) or tx hash (EVM 0x...)

No output schema declared.

No examples provided.

unit_convert ~135

Convert a value between units: length (m/km/mi/ft/in/yd/nmi + Russian verst/sazhen), mass (g/kg/lb/oz + pood/funt), area (m2/ft2/acre/hectare) and temperature (C/F/K). -> /x/util/convert. Pay-per-call ($0.001 USDC).

NameTypeReqDescription
fromstringyesSource unit, e.g. miles, kg, pood
tostringyesTarget unit, e.g. km, lb, celsius
valuenumberyesThe numeric value to convert

No output schema declared.

No examples provided.

unix_timestamp ~101

Convert between unix epoch and human time: pass seconds, milliseconds or an ISO date, get epoch (s+ms), ISO-8601 UTC and a formatted value in a target timezone. -> /x/util/timestamp. Pay-per-call ($0.001 USDC).

NameTypeReqDescription
tzstring–IANA timezone, e.g. America/Santiago (default UTC)
valuestringyesUnix seconds, unix ms, or an ISO date string

No output schema declared.

No examples provided.

x402_ecosystem_networks ~78

Network and payment-asset histogram of the live x402 ecosystem: which chains (CAIP-2 ids) and which USDC/other assets the indexed pay-per-call services accept, with counts. Sourced live from public indexes. -> /x/x402/networks. Pay-per-call ($0.005 USDC).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402_ecosystem_stats ~94

LIVE, sourced snapshot of x402 adoption across the public ecosystem: indexed pay-per-call service count, networks, payment assets, categories and USD price stats (min/median/mean/max), each with its source URL and fetchedAt. Aggregated from 402index.io + Coinbase CDP Bazaar + PayAI Bazaar. -> /x/x402/stats. Pay-per-call ($0.01 USDC).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the 47620 Multichain Data API — onchain, crypto, utilities… MCP server?

47620 Multichain Data API — onchain, crypto, utilities… is an MCP server listed in the public MCP registry as xyz.47620/multichain. x402 pay-per-call: onchain data (Solana/Base/Polygon), crypto market, JWT/unit utils, x402 stats. This page covers its hosted endpoint (https://47620.xyz/mcp/multichain).

Is the 47620 Multichain Data API — onchain, crypto, utilities… MCP server safe to use?

47620 Multichain Data API — onchain, crypto, utilities… scores 65 out of 100 on VerifyMCP. 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 Multichain Data API — onchain, crypto, utilities… MCP server expose?

47620 Multichain Data API — onchain, crypto, utilities… exposes 34 tools: snapshot, risk_check, should_pay, token_report, health, and 29 more. Their descriptions and schemas cost roughly 2,867 tokens of context every time the server is loaded.

Does the 47620 Multichain Data API — onchain, crypto, utilities… MCP server require authentication?

No. We connected to 47620 Multichain Data API — onchain, crypto, utilities… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 47620 Multichain Data API — onchain, crypto, utilities… MCP server still maintained?

47620 Multichain Data API — onchain, crypto, utilities… is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.