47620 MCP server

Which MCP servers are 47620's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to 47620

Whose server it is

Registry namexyz.47620/evm-dataverified in the MCP registry

The registry name sits under 47620.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26

Stateanswerschecked 2026-10-26
Tools18
Server calls itself47620-evm-data
Server version1.0.0
Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 163 ms.

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.
Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-27

INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
Answeredmeasuring2 of the 7 daily checks it takes to print a share
Median first answer497 ms
Space in an agent's context≈ 1,283 tokensthe definitions of all its tools (18), which an agent carries on every turn
Tool definitionsB · 83 of 100
Typed results0 of 18 toolsdeclared outputSchema: results come typed, read once

Not saying whether it only reads or can destroy: 18 of 18

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers18 tools · read 2026-10-26

base_health
base network health: chain id, latest block, gas price, native token USD price. Cheapest call. Pay-per-call ($0.002 USDC).
base_block
Header + summary for a base block by number (or "latest"): hash, timestamp, tx count, gas used, base fee. Pay-per-call ($0.005 USDC).
base_balance
Native balance + live USD value for any base address. Pay-per-call ($0.005 USDC).
base_stables
USDC/USDT/DAI balances for a base address in one call. Pay-per-call ($0.01 USDC).
base_token
Live price, liquidity, 24h volume + DEX pairs for any base ERC-20 token (plus onchain name/symbol/decimals). Pay-per-call ($0.02 USDC).
base_tx
Status (success/reverted), block, gas + transfer summary for a base tx hash. Pay-per-call ($0.01 USDC).
base_contract
Whether a base address is a contract, bytecode size + ERC-20 metadata. Pay-per-call ($0.01 USDC).
base_gas
Current base gas price (gwei + wei) + estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).
base_trending
Trending base DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).
polygon_health
polygon network health: chain id, latest block, gas price, native token USD price. Cheapest call. Pay-per-call ($0.002 USDC).
polygon_block
Header + summary for a polygon block by number (or "latest"): hash, timestamp, tx count, gas used, base fee. Pay-per-call ($0.005 USDC).
polygon_balance
Native balance + live USD value for any polygon address. Pay-per-call ($0.005 USDC).
polygon_stables
USDC/USDT/DAI balances for a polygon address in one call. Pay-per-call ($0.01 USDC).
polygon_token
Live price, liquidity, 24h volume + DEX pairs for any polygon ERC-20 token (plus onchain name/symbol/decimals). Pay-per-call ($0.02 USDC).
polygon_tx
Status (success/reverted), block, gas + transfer summary for a polygon tx hash. Pay-per-call ($0.01 USDC).
polygon_contract
Whether a polygon address is a contract, bytecode size + ERC-20 metadata. Pay-per-call ($0.01 USDC).
polygon_gas
Current polygon gas price (gwei + wei) + estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).
polygon_trending
Trending polygon DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "evm-data": {
      "type": "http",
      "url": "https://47620.xyz/mcp/evm"
    }
  }
}

Add it

Claude Code, in a terminal

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

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://47620.xyz/mcp/evm as a custom connector in the settings.

Also shipped through: npm

Other servers listed as 47620's

xyz.47620/multichainanswers, 52 toolsverified in the MCP registry
xyz.47620/solana-dataanswers, 52 toolsverified in the MCP registry

OpenAPI spec

195 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.