ethereum-wallet-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Get the current ETH balance of a wallet (read live from the chain). |
| list_walletsA | List all wallets owned by the authenticated user. |
| list_transactionsB | List the authenticated user's transactions (paged). |
| get_transactionA | Get details of a single transaction owned by the authenticated user. |
| create_walletB | Create a new Ethereum wallet for the authenticated user. |
| gas_priceA | Get the current gas price in Gwei. Public; no API key required. |
| validate_addressA | Validate an Ethereum address format. Public; no API key required. |
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
Each tool targets a distinct resource and action: balance reads, wallet listing/creation, transaction listing vs. single-transaction detail, plus two clearly public utility calls (gas price, address validation). There is no meaningful overlap between any pair, and the list/get distinction on transactions is explicit.
Five of seven tools follow a clean verb_noun pattern (get_balance, list_wallets, list_transactions, get_transaction, create_wallet, validate_address). The only deviation is gas_price, which uses a noun phrase rather than a verb, but it is still readable and unambiguous.
Seven tools is a tight, well-scoped surface for an Ethereum wallet server with no filler. Every tool maps to a distinct capability an agent would plausibly need.
Read paths and wallet creation are covered, but there is no send/transfer tool, no single-wallet detail or rename/delete operation, and no transaction submission or signing. An agent can inspect a wallet but cannot act on it, which is a notable gap for a wallet server.