Home / MCP registry index / io.github.47620-xyz/solana-data

47620 Solana Data

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

The registry describes it as: Pay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key.

Connect it

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

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

{
  "mcpServers": {
    "solana-data": {
      "url": "https://47620.xyz/mcp"
    }
  }
}

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

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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

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

Run this server? Show the check in your README

The badge reflects the latest weekly read:

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

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