Etherscan Api Mcp
Let your coding agent query Ethereum addresses, transactions, contracts, and on-chain metrics without hand-rolling Etherscan REST calls.
Overview
io.github.junct-bot/etherscan-api-mcp is a MCP server for the Build phase that exposes 71 Etherscan API tools for on-chain data, metrics, and analytics to your agent.
What is this MCP server?
- 71 MCP tools covering balances, transfers, contract metadata, gas, and block-level metrics via Etherscan
- Hosted streamable HTTP remote at etherscan-api.mcp.junct.dev—no local Node install required
- Version 1.1.0 with server.schema.json metadata for Claude Desktop–style MCP registries
- Suited for solo builders validating wallet activity, token flows, and contract deployments from the agent
- Open-source repo on GitHub under junct-bot/etherscan-api-mcp for auditing tool behavior
- 71 MCP tools documented for data, metrics, and on-chain analytics
- Server version 1.1.0
- Remote transport: streamable-http
What problem does it solve?
You waste cycles copying Etherscan endpoints into prompts and parsing JSON by hand whenever your agent needs real Ethereum state.
Who is it for?
Indie builders adding Ethereum read-only analytics, wallet history, or contract research into an MCP-enabled coding agent during product integration work.
Skip if: Teams that need private chain indexing, sub-second streaming, or trading execution without any external API key and rate limits.
What do I get? / Deliverables
Your agent can call standardized MCP tools for addresses, txs, and contracts so you ship chain-aware features faster with fewer bespoke API scripts.
- Agent-callable Etherscan operations for addresses, transactions, and metrics
- Faster integration of read-only Ethereum data into app prototypes
- Reduced custom REST glue code in your repository
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you wire this MCP into Claude Code or Cursor while implementing wallet dashboards, indexers, or compliance tooling—not during pure idea brainstorming. Integrations is the right subphase: the server is a remote HTTP MCP endpoint that exposes dozens of Etherscan API operations as agent-callable tools.
How it compares
Remote Etherscan MCP integration with 71 read tools—not a local blockchain node or a generic web-scraping skill.
Common Questions / FAQ
Who is etherscan-api-mcp for?
Solo builders and small teams using Claude Code, Cursor, or Codex who want Ethereum explorer data inside the agent while building dashboards, bots, or validation flows.
When should I use etherscan-api-mcp?
Use it during Build integrations when you need repeatable on-chain lookups—balances, transfers, contract info—without maintaining your own Etherscan client code.
How do I add etherscan-api-mcp to my agent?
Register the streamable HTTP remote URL https://etherscan-api.mcp.junct.dev/mcp in your MCP client config, supply an Etherscan API key per the server docs, then restart the agent so the 71 tools appear.