Home / MCP registry index / xyz.47620/multichain

47620 Multichain Data API — onchain, crypto, utilities, x402 stats

xyz.47620/multichain in the official MCP registry. Endpoint https://47620.xyz/mcp/multichain. Source: github.com/47620-xyz/solana-data-mcp.

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

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http multichain https://47620.xyz/mcp/multichain

{
  "mcpServers": {
    "multichain": {
      "url": "https://47620.xyz/mcp/multichain"
    }
  }
}

code --add-mcp '{"name":"multichain","type":"http","url":"https://47620.xyz/mcp/multichain"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

snapshot risk_check should_pay token_report health balance tx token gas trending contract trust_check crypto_price crypto_ohlcv crypto_indicators crypto_derivatives crypto_orderbook crypto_deep crypto_prices crypto_analytics jwt_decode unit_convert qr_generate unix_timestamp sha256_fingerprint x402_ecosystem_stats x402_ecosystem_networks solana_snapshot solana_risk_check solana_token_report solana_health solana_token solana_account solana_tx solana_trending account portfolio_multichain wallet_balances_multichain wallet_reliability_json tx_receipt tx_history gas_multichain token_risk_evm defi_arbitrage nft_holdings defi_yields stablecoin_peg token_research wallet_security payment_evidence payment_verify opportunity_feed

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 5f1215627b9be305. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/xyz-47620-multichain/badge.svg)](https://lazaretto.dev/mcp-registry/xyz-47620-multichain)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers