Home / MCP registry index / io.etherscan/etherscan-mcp

Etherscan

io.etherscan/etherscan-mcp in the official MCP registry. Endpoint https://mcp-keyless.etherscan.io/mcp.

The registry describes it as: Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs.

We read its 17 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http etherscan-mcp https://mcp-keyless.etherscan.io/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "etherscan-mcp": {
      "url": "https://mcp-keyless.etherscan.io/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"etherscan-mcp","type":"http","url":"https://mcp-keyless.etherscan.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_native_balance get_transactions get_internal_transactions get_token_transfers resolve_ens_name get_contract_source get_contract_abi get_contract_creation get_transaction_receipt_status get_transaction_status get_gas_oracle get_block_by_timestamp get_supported_chains get_logs get_transaction_by_hash get_transaction_receipt render_etherscan_widget

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-etherscan-etherscan-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-etherscan-etherscan-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26