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 (obtain 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-contract-codeC | Get the source code 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 7 tools
Every tool has a clearly distinct purpose targeting specific Ethereum-related operations: balance checking, contract ABI/code retrieval, ENS resolution, gas price fetching, token transfer history, and transaction history. No overlap exists between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., check-balance, get-contract-abi, get-ens-name). The naming is uniform across all seven tools, using clear action verbs like 'check' and 'get' paired with specific nouns.
Seven tools is well-scoped for an Etherscan server, covering essential Ethereum blockchain interactions without being overwhelming. Each tool serves a distinct and useful purpose, such as balance checks, contract data retrieval, and transaction history, making the count appropriate for the domain.
The tool set provides strong coverage for common Ethereum queries, including balance, contract details, ENS, gas prices, and transaction histories. A minor gap exists in write operations (e.g., sending transactions or interacting with contracts), but for a read-focused server, this is reasonable and agents can work around it.