MCP Etherscan Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ETHERSCAN_API_KEY | Yes | An Etherscan API key used to access blockchain data. You can get one at https://etherscan.io/apis. One API key works for all 72+ supported networks. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check-balanceA | Check the ETH balance of an Ethereum address across 70+ supported networks |
| get-transactionsC | Get recent transactions for an Ethereum address across 70+ supported networks |
| get-token-transfersC | Get ERC20 token transfers for an Ethereum address |
| get-contract-abiB | Get the ABI for a smart contract |
| get-gas-pricesB | Get current gas prices in Gwei |
| get-ens-nameA | Get the ENS name for an Ethereum address (mainnet only) |
| get-mined-blocksB | Get blocks mined by an address |
| get-internal-transactionsB | Get internal transactions for an Ethereum address |
| get-block-detailsC | Get detailed information about a specific block |
| get-block-rewardC | Get reward information for a specific block |
| get-contract-sourceA | Get the source code and metadata for a verified smart contract |
| get-contract-creationC | Get creation information for a specific contract address |
| verify-contractB | Submit a contract for source code verification |
| check-verificationB | Check the status of a contract verification request |
| verify-proxyC | Submit a proxy contract for verification |
| get-verified-contractsC | Get recently verified contracts |
| get-beacon-withdrawalsB | Get beacon chain withdrawals for an Ethereum address (ETH 2.0 staking withdrawals) |
| get-token-infoA | Get comprehensive information about an ERC20/ERC721/ERC1155 token including metadata and social links |
| get-token-holdersB | Get top token holders for an ERC20 token with their balances and ownership percentage |
| get-token-portfolioA | Get all token balances for an address across ERC20/ERC721/ERC1155 standards |
| get-logsB | Get event logs filtered by address and/or topics with advanced filtering options |
| get-network-statsA | Get network statistics including ETH supply, ETH2 staking, price, and market cap |
| get-daily-statsB | Get daily transaction count statistics for a date range |
| list-networksA | List all supported blockchain networks (70+) with their chain IDs and native currencies |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Each tool targets a unique aspect of Ethereum blockchain data: balances, blocks, contracts, tokens, transactions, and more. Descriptions clearly differentiate similar tools like get-transactions, get-internal-transactions, and get-token-transfers.
Most tools follow a 'get_' prefix pattern, but there are a few using 'check_', 'list_', and 'verify_'. While all are verb_noun, the inconsistency in verb choice prevents a perfect score.
24 tools is slightly above the typical 3-15 range, but the broad domain of Ethereum data (accounts, blocks, contracts, tokens, etc.) justifies the count. Each tool serves a distinct purpose.
The surface covers nearly all common Etherscan API operations: balance, transactions, blocks, contract verification, token data, logs, ENS, gas, and network stats. No obvious gaps for the intended domain.