Riding the v2 API is the right call — one key, many chains, no per-network server. Two things to check before you commit: chain coverage varies by endpoint, and Pro-tier calls are on the author's list rather than in the build. For read-only exploration on a supported chain, it is a short setup.
A dynamic MCP server over Etherscan's API and services. It targets the Etherscan v2 API, which serves many chains from one key, so on-chain lookups — balances, transactions, contract data — happen inside the conversation.
- Access to the Etherscan v2 API surface from an MCP client, driven by your own Etherscan key
- The multi-chain v2 endpoint, so the same server covers Etherscan's supported chain list rather than mainnet alone
- Local inspection before wiring it into a client: `npx fastmcp dev src/index.ts` runs it in a terminal, `npx fastmcp inspect src/index.ts` opens the MCP Inspector web UI
An Etherscan API key in `ETHERSCAN_API_KEY`. The npm package is private, so clone the repo and launch the TypeScript entry point directly — the documented Claude Desktop config runs `npx tsx /PATH/TO/YOUR_PROJECT/src/index.ts`. Two limits to know before you plan around it: not every endpoint is available on every chain (Etherscan publishes the support grid), and the Pro API is listed as not yet supported. Version 1.0.0.