MCP Crypto Wallet EVM
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 |
|---|---|
| wallet_provider_setB | Set the provider URL. By default, the provider URL is set to the ETH mainnet or the URL set in the PROVIDER_URL environment variable. |
| wallet_create_randomC | Create a new wallet with a random private key |
| wallet_from_private_keyC | Create a wallet from a private key |
| wallet_create_mnemonic_phraseC | Create a mnemonic phrase |
| wallet_from_mnemonicC | Create a wallet from a mnemonic phrase |
| wallet_from_encrypted_jsonC | Create a wallet by decrypting an encrypted JSON wallet |
| wallet_encryptC | Encrypt a wallet with a password |
| wallet_get_addressC | Get the wallet address |
| wallet_get_public_keyC | Get the wallet public key |
| wallet_get_private_keyC | Get the wallet private key (with appropriate security warnings) |
| wallet_get_balanceC | Get the balance of the wallet |
| wallet_get_chain_idB | Get the chain ID the wallet is connected to |
| wallet_get_gas_priceC | Get the current gas price |
| wallet_get_transaction_countC | Get the number of transactions sent from this account (nonce) |
| wallet_callC | Call a contract method without sending a transaction |
| wallet_send_transactionC | Send a transaction |
| wallet_sign_transactionB | Sign a transaction without sending it |
| wallet_populate_transactionC | Populate a transaction with missing fields |
| wallet_sign_messageC | Sign a message |
| wallet_sign_typed_dataC | Sign typed data (EIP-712) |
| wallet_verify_messageC | Verify a signed message |
| wallet_verify_typed_dataC | Verify signed typed data |
| provider_get_blockC | Get a block by number or hash |
| provider_get_transactionC | Get a transaction by hash |
| provider_get_transaction_receiptC | Get a transaction receipt |
| provider_get_codeC | Get the code at an address |
| provider_get_storage_atC | Get the storage at a position for an address |
| provider_estimate_gasC | Estimate the gas required for a transaction |
| provider_get_logsC | Get logs that match a filter |
| provider_get_ens_resolverC | Get the ENS resolver for a name |
| provider_lookup_addressC | Lookup the ENS name for an address |
| provider_resolve_nameC | Resolve an ENS name to an address |
| network_get_networkC | Get the current network information |
| network_get_block_numberB | Get the current block number |
| network_get_fee_dataB | Get the current fee data (base fee, max priority fee, etc.) |
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 35 tools
Most tools have distinct purposes with clear resource-action pairs (e.g., network_get_block_number vs. wallet_get_balance), but some overlap exists in provider and wallet operations that could cause confusion, such as provider_get_transaction and wallet_get_transaction_count both dealing with transaction data. Descriptions help clarify, but the boundaries between network, provider, and wallet categories are not always sharp.
Tool names follow a highly consistent verb_noun pattern with clear prefixes (network_, provider_, wallet_) that group related functions. All names use snake_case uniformly, making them predictable and easy to parse. This consistency aids in understanding the tool set's structure and purpose.
With 35 tools, the count is borderline high for a crypto wallet server, potentially overwhelming for agents. While the domain (EVM wallet operations) is broad, covering network, provider, and wallet functions, the number feels heavy and could be streamlined. It's not extreme, but it approaches the upper limit of reasonable scope.
The tool set provides comprehensive coverage for EVM wallet operations, including network interactions, provider queries, wallet creation/management, transaction handling, and signing/verification. All essential CRUD and lifecycle actions are present, with no obvious gaps that would hinder agent workflows in this domain.