Etherscan MCP
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 targeting different token-related queries, but get_token_holders and get_token_holders_count could be confused as they both retrieve holder information. The descriptions clarify the difference (list vs count), but the overlap in naming might cause misselection.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_chain_id, get_token_balance). The naming is highly predictable and readable throughout the set, with no deviations in style or convention.
With 6 tools, the count is reasonable for an Etherscan-focused server, covering chain info, RPC endpoints, and token data. It feels slightly thin for a full blockchain explorer, but it's well-scoped for the provided token and chain utilities.
The tools cover token balances, holders, and supply, plus chain and RPC info, but there are notable gaps for a broader Etherscan domain. Missing operations include transaction lookups, contract interactions, and gas/price queries, which are common in blockchain tools, limiting coverage to a narrow subset.