Etherscan MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_filtered_rpc_listC | Get a filtered list of RPC endpoints for a given chain ID |
| get_chain_idB | Get the chain ID for a given chain name |
| get_total_supplyB | Get the total supply of a token given its address |
| get_token_balanceC | Get the balance of a specific token for a specific address |
| get_token_holdersC | Get the token holders for a given token address |
| get_token_holders_countC | Get the number of token holders for a given token 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
Most tools have distinct purposes, such as get_chain_id for chain identification and get_token_balance for balance queries. However, get_token_holders and get_token_holders_count could be confused as they both relate to token holders, though the descriptions clarify one provides a list and the other a count.
All tool names follow a consistent verb_noun pattern with 'get_' prefix, such as get_chain_id and get_token_balance. This uniformity makes the set predictable and easy to understand, with no deviations in style or convention.
With 6 tools, the count is reasonable for an Etherscan-related server, covering key blockchain queries. It is slightly lean but not overly sparse, as each tool serves a specific function without obvious bloat or redundancy.
The tools cover basic token and chain queries, such as balances and holders, but there are notable gaps. For an Etherscan domain, missing operations like transaction lookups, contract interactions, or event logs limit the surface, though agents can work around this for simple tasks.