47620 Base + Polygon Data API MCP server
xyz.47620/evm-data47620.xyzstreamable-httpv1.0.0Scanned
Pay-per-call Base and Polygon onchain data over x402 for AI agents.
18 tools: 16 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
16 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the 47620 Base + Polygon Data API MCP server can do
The 47620 Base + Polygon Data API MCP server is published by 47620.xyz, a domain the MCP Registry verified. It has 18 tools. It can create or change data (16 tools: base_health, base_block, base_balance, base_stables and 12 more), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
18 tools
Changes things 16Claude Code: ask
base_balanceNative balance + live USD value for any base address.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Native balance + live USD value for any base address. Pay-per-call ($0.005 USDC).
base_blockHeader + summary for a base block by number (or "latest"): hash, timestamp, tx count, gas used, base fee.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_contractWhether a base address is a contract, bytecode size + ERC-20 metadata.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Whether a base address is a contract, bytecode size + ERC-20 metadata. Pay-per-call ($0.01 USDC).
base_gasCurrent base gas price (gwei + wei) + estimated cost of a 21k native transfer.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Current base gas price (gwei + wei) + estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).
base_healthbase network health: chain id, latest block, gas price, native token USD price.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it base network health: chain id, latest block, gas price, native token USD price. Cheapest call. Pay-per-call ($0.002 USDC).
base_stablesUSDC/USDT/DAI balances for a base address in one call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it USDC/USDT/DAI balances for a base address in one call. Pay-per-call ($0.01 USDC).
base_tokenLive price, liquidity, 24h volume + DEX pairs for any base ERC-20 token (plus onchain name/symbol/decimals).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_trendingTrending base DEX pairs by 24h volume (DexScreener boosts).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Trending base DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).
polygon_balanceNative balance + live USD value for any polygon address.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Native balance + live USD value for any polygon address. Pay-per-call ($0.005 USDC).
polygon_blockHeader + summary for a polygon block by number (or "latest"): hash, timestamp, tx count, gas used, base fee.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_contractWhether a polygon address is a contract, bytecode size + ERC-20 metadata.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Whether a polygon address is a contract, bytecode size + ERC-20 metadata. Pay-per-call ($0.01 USDC).
polygon_gasCurrent polygon gas price (gwei + wei) + estimated cost of a 21k native transfer.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Current polygon gas price (gwei + wei) + estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).
polygon_healthpolygon network health: chain id, latest block, gas price, native token USD price.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it polygon network health: chain id, latest block, gas price, native token USD price. Cheapest call. Pay-per-call ($0.002 USDC).
polygon_stablesUSDC/USDT/DAI balances for a polygon address in one call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it USDC/USDT/DAI balances for a polygon address in one call. Pay-per-call ($0.01 USDC).
polygon_tokenLive price, liquidity, 24h volume + DEX pairs for any polygon ERC-20 token (plus onchain name/symbol/decimals).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_trendingTrending polygon DEX pairs by 24h volume (DexScreener boosts).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Trending polygon DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).
Only reads 2Show 2 read-only tools
base_txStatus (success/reverted), block, gas + transfer summary for a base tx hash.No findings
Why it is in this group
- The description's first verb is "status": a word for reading.
Description, as the server wrote it Status (success/reverted), block, gas + transfer summary for a base tx hash. Pay-per-call ($0.01 USDC).
polygon_txStatus (success/reverted), block, gas + transfer summary for a polygon tx hash.No findings
Why it is in this group
- The description's first verb is "status": a word for reading.
Description, as the server wrote it Status (success/reverted), block, gas + transfer summary for a polygon tx hash. Pay-per-call ($0.01 USDC).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 16
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 16 tools that change things (16 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://47620.xyz/mcp/evm: tools/list returned 18 tools to an anonymous client, including base_health (write), base_block (write), base_balance (write), base_stables (write), base_token (write) and 11 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http evm-data https://47620.xyz/mcp/evmclaude mcp add --transport http evm-data https://47620.xyz/mcp/evmRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__evm-data__base_tx",
"mcp__evm-data__polygon_tx"
],
"ask": [
"mcp__evm-data__base_health",
"mcp__evm-data__base_block",
"mcp__evm-data__base_balance",
"mcp__evm-data__base_stables",
"mcp__evm-data__base_token",
"mcp__evm-data__base_contract",
"mcp__evm-data__base_gas",
"mcp__evm-data__base_trending",
"mcp__evm-data__polygon_health",
"mcp__evm-data__polygon_block",
"mcp__evm-data__polygon_balance",
"mcp__evm-data__polygon_stables",
"mcp__evm-data__polygon_token",
"mcp__evm-data__polygon_contract",
"mcp__evm-data__polygon_gas",
"mcp__evm-data__polygon_trending"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as evm-data. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/xyz.47620/evm-data/verify?hash=e83c7fba4516305cd0236ff314966b905f587f248ac0407cf2e74cfa6a26faa7" | jq -e '.changed == false'Pinned hash e83c7fba4516, from Nov 18, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/xyz.47620/evm-data/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/xyz.47620/evm-data)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.
47620 Base + Polygon Data API MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the 47620 Base + Polygon Data API MCP server safe?
- No scan can promise that. What its definitions show: 18 tools, 16 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the 47620 Base + Polygon Data API MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the 47620 Base + Polygon Data API MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the 47620 Base + Polygon Data API MCP server have?
- 18 tools: 16 write, 2 read. base_health, base_block, base_balance, base_stables, base_token, base_contract, base_gas, base_trending and 10 more.
Does the 47620 Base + Polygon Data API MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the 47620 Base + Polygon Data API MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the 47620 Base + Polygon Data API MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.