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.

Etherscan

NPM · @PIPEWORX/MCP-ETHERSCAN · 2 COMPONENTS

Etherscan MCP — multichain block-explorer API (Etherscan V2)

+4 this week 84 Trust /100

Last scanned (6 hours ago)

Scores higher than 81% 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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-etherscan). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 505 tokens (~101/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +2
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: unverified → fail ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: unverified → 0.10 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 80

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-etherscan@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-etherscan
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-etherscan/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3635929223
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8778248c3851c9db5e978acc5679206ac1162fdcf4809d97e995211b8ef8a82561560a9aa41be299e00a3f37cb3c34484cbd10f9a34e6b2b7203f3538

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~452 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
get_balance ~99

Native-token balance for an address on a supported EVM chain. Defaults to Ethereum mainnet. Accepts chain by slug (ethereum, polygon, bsc, base, arbitrum, optimism, avalanche, fantom, gnosis, linea, scroll, zksync, blast, mantle) or numeric chain ID.

NameTypeReqDescription
addressstringyes0x address
chainstring–Chain slug or numeric chain ID (default ethereum)

No output schema declared.

No examples provided.

get_contract_abi ~50

Verified contract ABI as JSON (if the contract is verified on Etherscan).

NameTypeReqDescription
addressstringyesContract address
chainstring–Chain slug or chain ID (default ethereum)

No output schema declared.

No examples provided.

get_contract_source ~47

Verified contract source code, compiler version, optimization settings, and license.

NameTypeReqDescription
addressstringyesContract address
chainstring–Chain slug or chain ID (default ethereum)

No output schema declared.

No examples provided.

get_token_balance ~61

ERC-20 token balance for an address against a specific token contract.

NameTypeReqDescription
addressstringyesHolder address
chainstring–Chain slug or numeric chain ID (default ethereum)
contract_addressstringyesERC-20 contract address

No output schema declared.

No examples provided.

list_transactions ~195

List transactions for an address. type controls which list: "normal" (regular EOA txs), "internal" (contract-internal value transfers), "erc20" (ERC-20 transfers), "erc721" (NFT transfers), "erc1155" (multi-token transfers).

NameTypeReqDescription
addressstringyesAddress to inspect
chainstring–Chain slug or chain ID (default ethereum)
endblocknumber–End block (default latest = 99999999)
offsetnumber–Results per page (default 25, max 10000)
pagenumber–Page number (default 1)
sortstring–asc | desc (default desc)
startblocknumber–Start block (default 0)
typestring–normal | internal | erc20 | erc721 | erc1155 (default normal)

No output schema declared.

No examples provided.

Install

How do I install the Etherscan MCP server?

Etherscan runs locally as an npm package, launched with npx -y @pipeworx/mcp-etherscan. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-etherscan

# add to Claude Code
claude mcp add pipeworx-io-etherscan -- npx -y @pipeworx/mcp-etherscan
Common questions

What is the Etherscan MCP server?

Etherscan is an MCP server listed in the public MCP registry as io.github.pipeworx-io/etherscan. Etherscan MCP, multichain block-explorer API (Etherscan V2). This page covers its npm package (@pipeworx/mcp-etherscan).

Is the Etherscan MCP server safe to use?

Etherscan scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Etherscan MCP server expose?

Etherscan exposes 5 tools: get_balance, get_token_balance, list_transactions, get_contract_abi, get_contract_source. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.

Is the Etherscan MCP server still maintained?

Etherscan is still listed as active in the MCP registry. We last reached this channel on 5 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 Etherscan MCP server under?

Etherscan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.