47620 Base + Polygon Data API
REMOTE · 47620.XYZ · 2 COMPONENTS · SCANNED SEP 25
Pay-per-call Base and Polygon onchain data over x402 for AI agents.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 846 tokens (~47/item across 18 items; 18 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
How do I install the 47620 Base + Polygon Data API MCP server?
47620 Base + Polygon Data API is a hosted endpoint at https://47620.xyz/mcp/evm, 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
claude mcp add --transport http xyz-47620-evm-data 'https://47620.xyz/mcp/evm'
{
"mcpServers": {
"xyz-47620-evm-data": {
"url": "https://47620.xyz/mcp/evm"
}
}
} {
"servers": {
"xyz-47620-evm-data": {
"type": "http",
"url": "https://47620.xyz/mcp/evm"
}
}
} [mcp_servers.xyz-47620-evm-data] url = "https://47620.xyz/mcp/evm"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-47620-evm-data": {
"type": "remote",
"url": "https://47620.xyz/mcp/evm",
"enabled": true
}
}
} openclaw mcp add xyz-47620-evm-data --url 'https://47620.xyz/mcp/evm' --transport streamable-http
mcp_servers:
xyz-47620-evm-data:
url: "https://47620.xyz/mcp/evm" {
"McpServers": {
"xyz-47620-evm-data": {
"Transport": "http",
"Url": "https://47620.xyz/mcp/evm"
}
}
} assistant mcp add xyz-47620-evm-data -t streamable-http -u 'https://47620.xyz/mcp/evm'
{
"mcpServers": {
"xyz-47620-evm-data": {
"type": "http",
"url": "https://47620.xyz/mcp/evm"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 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
- 24 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Sept 26 63
First indexed and scored.
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 25 Sept 2026 · Probed https://47620.xyz/mcp/evm
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/evm | Verified | 200 | |
| http (plaintext) | http://47620.xyz/mcp/evm | HTTPS enforced | 308 | https://47620.xyz/mcp/evm |
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 →
base_balance ~41
Native balance + live USD value for any base address. Pay-per-call ($0.005 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | base address (0x...) |
No output schema declared.
No examples provided.
base_block ~57
Header + summary for a base block by number (or "latest"): hash, timestamp, tx count, gas used, base fee. Pay-per-call ($0.005 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | – | Block number or "latest" |
No output schema declared.
No examples provided.
base_contract ~47
Whether a base address is a contract, bytecode size + ERC-20 metadata. Pay-per-call ($0.01 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | base address (0x...) |
No output schema declared.
No examples provided.
base_gas ~40
Current base gas price (gwei + wei) + estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
base_health ~39
base network health: chain id, latest block, gas price, native token USD price. Cheapest call. Pay-per-call ($0.002 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
base_stables ~48
USDC/USDT/DAI balances for a base address in one call. Pay-per-call ($0.01 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | base address (0x...) |
No output schema declared.
No examples provided.
base_token ~62
Live price, liquidity, 24h volume + DEX pairs for any base ERC-20 token (plus onchain name/symbol/decimals). Pay-per-call ($0.02 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | base ERC-20 token address |
No output schema declared.
No examples provided.
base_trending ~41
Trending base DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
base_tx ~48
Status (success/reverted), block, gas + transfer summary for a base tx hash. Pay-per-call ($0.01 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Transaction hash (0x...) |
No output schema declared.
No examples provided.
polygon_balance ~41
Native balance + live USD value for any polygon address. Pay-per-call ($0.005 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | polygon address (0x...) |
No output schema declared.
No examples provided.
polygon_block ~57
Header + summary for a polygon block by number (or "latest"): hash, timestamp, tx count, gas used, base fee. Pay-per-call ($0.005 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | – | Block number or "latest" |
No output schema declared.
No examples provided.
polygon_contract ~47
Whether a polygon address is a contract, bytecode size + ERC-20 metadata. Pay-per-call ($0.01 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | polygon address (0x...) |
No output schema declared.
No examples provided.
polygon_gas ~40
Current polygon gas price (gwei + wei) + estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
polygon_health ~39
polygon network health: chain id, latest block, gas price, native token USD price. Cheapest call. Pay-per-call ($0.002 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
polygon_stables ~48
USDC/USDT/DAI balances for a polygon address in one call. Pay-per-call ($0.01 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | polygon address (0x...) |
No output schema declared.
No examples provided.
polygon_token ~62
Live price, liquidity, 24h volume + DEX pairs for any polygon ERC-20 token (plus onchain name/symbol/decimals). Pay-per-call ($0.02 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | polygon ERC-20 token address |
No output schema declared.
No examples provided.
polygon_trending ~41
Trending polygon DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
polygon_tx ~48
Status (success/reverted), block, gas + transfer summary for a polygon tx hash. Pay-per-call ($0.01 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Transaction hash (0x...) |
No output schema declared.
No examples provided.
What is the 47620 Base + Polygon Data API MCP server?
47620 Base + Polygon Data API is an MCP server listed in the public MCP registry as xyz.47620/evm-data. Pay-per-call Base and Polygon onchain data over x402 for AI agents. This page covers its hosted endpoint (https://47620.xyz/mcp/evm).
Is the 47620 Base + Polygon Data API MCP server safe to use?
47620 Base + Polygon Data API scores 64 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 Base + Polygon Data API MCP server expose?
47620 Base + Polygon Data API exposes 18 tools: base_health, base_block, base_balance, base_stables, base_token, and 13 more. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Does the 47620 Base + Polygon Data API MCP server require authentication?
No. We connected to 47620 Base + Polygon Data API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 47620 Base + Polygon Data API MCP server still maintained?
47620 Base + Polygon Data API is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.