Etherscan Tools MCP Server

Provides Ethereum blockchain data tools via Etherscan's API for interacting with the Ethereum blockchain. Exposed over MCP by the etherscan tools mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP (Model Context Protocol) server that provides Ethereum blockchain data tools via Etherscan's API. Features include checking ETH balances, viewing transaction history, tracking ERC20 transfers, fetching contract ABIs, monitoring gas prices, and resolving ENS names.

• Balance Checking — Get ETH balance for any Ethereum address
• Transaction History — View recent transactions with detailed information
• Token Transfers — Track ERC20 token transfers with token details
• Contract ABI — Fetch smart contract ABIs for development
• Gas Prices — Monitor current gas prices (Safe Low, Standard, Fast)
• ENS Resolution — Resolve Ethereum addresses to ENS names

Its toolset

Everything the assistant can do here goes through one of these:

• Input — Ethereum address
• Output — ETH balance in both Wei and ETH

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need one environment variable: ETHERSCAN_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 18 - An Etherscan API key (get one at https://etherscan.io/apis)

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Etherscan Tools's toolset — Input, Output — is a fair guide to whether it matches your workflow. It is maintained by 5ajaki; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the etherscan tools mcp server does with a few real requests.