Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

47620 Base + Polygon Data API

NPM · 47620-EVM-MCP · 2 COMPONENTS

Pay-per-call Base and Polygon onchain data over x402 for AI agents.

0 this week 78 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 40 of 120 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 58 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 924 tokens (~51/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 18 Nov 26 0
    • Stability: 0.97 → pass security
  • 17 Nov 26 0
    • Stability: pass → 0.97 functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 −2
    • Stability: pass → 0.80 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/47620-evm-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 120 packages
Packages resolved 120
Stale 40
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~924 tokens

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 →

Tool Tokens
base_balance ~48

Native balance and live USD value for any base address. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
addressstringyesbase address (0x...)
fieldsstring––

No output schema declared.

No examples provided.

base_block ~64

Header + summary for a base block by number (or "latest"): hash, timestamp, tx count, gas used, base fee. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
fieldsstring––
numberstring–Block number or "latest"

No output schema declared.

No examples provided.

base_contract ~50

Whether a base address is a contract, bytecode size, and ERC-20 metadata if applicable. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
addressstringyesbase address (0x...)

No output schema declared.

No examples provided.

base_gas ~47

Current base gas price (gwei + wei) and estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
fieldsstring––

No output schema declared.

No examples provided.

base_health ~51

base network health: chain id, latest block, gas price and native token USD price. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
fieldsstring–Optional comma-separated subset of fields to return

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).

NameTypeReqDescription
addressstringyesbase address (0x...)

No output schema declared.

No examples provided.

base_token ~62

Live price, liquidity, 24h volume and DEX pairs for any base ERC-20 token (plus onchain name/symbol/decimals). Pay-per-call ($0.02 USDC).

NameTypeReqDescription
tokenstringyesbase ERC-20 token address

No output schema declared.

No examples provided.

base_trending ~48

Trending base DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).

NameTypeReqDescription
fieldsstring––

No output schema declared.

No examples provided.

base_tx ~44

Status, block, gas and transfer summary for a base transaction hash. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
hashstringyesTransaction hash (0x...)

No output schema declared.

No examples provided.

polygon_balance ~48

Native balance and live USD value for any polygon address. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
addressstringyespolygon address (0x...)
fieldsstring––

No output schema declared.

No examples provided.

polygon_block ~64

Header + summary for a polygon block by number (or "latest"): hash, timestamp, tx count, gas used, base fee. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
fieldsstring––
numberstring–Block number or "latest"

No output schema declared.

No examples provided.

polygon_contract ~50

Whether a polygon address is a contract, bytecode size, and ERC-20 metadata if applicable. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
addressstringyespolygon address (0x...)

No output schema declared.

No examples provided.

polygon_gas ~47

Current polygon gas price (gwei + wei) and estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).

NameTypeReqDescription
fieldsstring––

No output schema declared.

No examples provided.

polygon_health ~51

polygon network health: chain id, latest block, gas price and native token USD price. Pay-per-call ($0.002 USDC).

NameTypeReqDescription
fieldsstring–Optional comma-separated subset of fields to return

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).

NameTypeReqDescription
addressstringyespolygon address (0x...)

No output schema declared.

No examples provided.

polygon_token ~62

Live price, liquidity, 24h volume and DEX pairs for any polygon ERC-20 token (plus onchain name/symbol/decimals). Pay-per-call ($0.02 USDC).

NameTypeReqDescription
tokenstringyespolygon ERC-20 token address

No output schema declared.

No examples provided.

polygon_trending ~48

Trending polygon DEX pairs by 24h volume (DexScreener boosts). Fresh feed for agents. Pay-per-call ($0.02 USDC).

NameTypeReqDescription
fieldsstring––

No output schema declared.

No examples provided.

polygon_tx ~44

Status, block, gas and transfer summary for a polygon transaction hash. Pay-per-call ($0.01 USDC).

NameTypeReqDescription
hashstringyesTransaction hash (0x...)

No output schema declared.

No examples provided.

Install

How do I install the 47620 Base + Polygon Data API MCP server?

47620 Base + Polygon Data API runs locally as an npm package, launched with npx -y 47620-evm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · 47620-evm-mcp

# add to Claude Code
claude mcp add xyz-47620-evm-data -- npx -y 47620-evm-mcp
Common questions

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 npm package (47620-evm-mcp).

Is the 47620 Base + Polygon Data API MCP server safe to use?

47620 Base + Polygon Data API scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 924 tokens of context every time the server is loaded.

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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the 47620 Base + Polygon Data API MCP server under?

47620 Base + Polygon Data API declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the 47620 Base + Polygon Data API MCP server?

VerifyMCP ran 15 checks on 47620 Base + Polygon Data API, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about 47620 Base + Polygon Data API: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.