MCP Etherscan Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ETHERSCAN_API_KEY | Yes | Your Etherscan API key (get one at https://etherscan.io/apis) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check-balanceB | Check the ETH balance of an Ethereum address |
| get-transactionsB | Get recent transactions for an Ethereum address |
| get-token-transfersC | Get ERC20 token transfers for an Ethereum address |
| get-contract-abiC | Get the ABI for a smart contract |
| get-gas-pricesA | Get current gas prices in Gwei |
| get-ens-nameB | Get the ENS name for an Ethereum address |
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 6 tools
Each tool has a clearly distinct purpose targeting different Ethereum-related queries: balance checks, contract ABI retrieval, ENS name lookup, gas price monitoring, token transfer history, and transaction history. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., check-balance, get-contract-abi, get-ens-name). This uniformity enhances readability and predictability, allowing agents to easily understand and navigate the tool set without confusion from mixed naming conventions.
With 6 tools, the server is well-scoped for an Etherscan-like interface, covering essential Ethereum operations without being overwhelming or sparse. Each tool serves a distinct and useful function, making the count appropriate for the domain and typical agent workflows.
The tool set covers core Ethereum functionalities such as address queries, contract interactions, and network data, but has minor gaps. For example, it lacks tools for checking internal transactions, verifying contract source code, or fetching block information, which could limit some advanced use cases, though agents can still perform most common tasks effectively.