network_get_block_number
Get the current block number
LABSCO SUMMARY
Key handling and chain reads answer to the same set of calls.
Nothing is configured as a credential here; keys, mnemonics and passwords travel as tool arguments instead. wallet_get_private_key is part of the set, and its own description notes the security warnings that accompany it. Until PROVIDER_URL or wallet_provider_set names another endpoint, every read goes to ETH mainnet.
What it is
An EVM wallet server: wallet construction and signing on one side, provider and network reads on the other.
What you get
- Wallets from a random key, an existing private key, a generated mnemonic phrase, or an encrypted JSON file opened with its password — plus re-encryption under a password.
- Wallet readouts: address, public key, private key, balance at a block tag, chain ID, current gas price and transaction count.
- Transactions handled in stages: call a contract method without sending, populate missing fields, sign without sending, or send.
- Message signing and verification on both sides, including EIP-712 typed data.
- Provider reads: a block by number or hash, a transaction, its receipt, contract code, storage at a position, a gas estimate and logs matching a filter.
- ENS in both directions along with the resolver for a name, and network-level reads of the current network, block number and fee data.
Requirements
A provider endpoint if ETH mainnet is not what you want — the default comes from the PROVIDER_URL environment variable or from wallet_provider_set. The signing tools need a wallet built first, which means a private key, a mnemonic phrase, or an encrypted JSON file and its password.
Setup effort
One command — npx @mcp-dockmaster/mcp-cryptowallet-evm
USE CASES
01
Standing up a wallet the server can sign with
Generate a new key or bring an existing one back from its mnemonic or encrypted file, confirm the address, and re-encrypt it for storage.
02
Pricing a transaction before committing to it
Check the balance, get a gas estimate for the exact transaction, compare it against current gas price and fee data, and let the wallet fill in the rest.
03
Following a transfer you just sent through to its receipt
Send it, look the transaction up by hash, wait for the receipt, and check the block number to see how far behind the head it is.
04
Reading contract state without spending anything
Call a method for its return value, confirm there is code at the address, read a storage slot directly, and pull the events matching a filter.
05
Checking a signature somebody handed you
Verify plain message signatures and EIP-712 typed data against the address that should have signed, and produce either kind when it is your turn.
06
Going from an ENS name to whatever is behind it
Resolve the name to an address, go back the other way from an address, and read the resolver contract that answers for the name.
35 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
network_get_fee_data
Get the current fee data (base fee, max priority fee, etc.)
network_get_network
Get the current network information
provider_estimate_gas
Estimate the gas required for a transaction
provider_get_block
Get a block by number or hash
provider_get_code
Get the code at an address
provider_get_ens_resolver
Get the ENS resolver for a name
provider_get_logs
Get logs that match a filter
provider_get_storage_at
Get the storage at a position for an address
provider_get_transaction
Get a transaction by hash
provider_get_transaction_receipt
Get a transaction receipt
provider_lookup_address
Lookup the ENS name for an address
provider_resolve_name
Resolve an ENS name to an address
wallet_call
Call a contract method without sending a transaction
wallet_create_mnemonic_phrase
Create a mnemonic phrase
wallet_create_random
Create a new wallet with a random private key
wallet_encrypt
Encrypt a wallet with a password
wallet_from_encrypted_json
Create a wallet by decrypting an encrypted JSON wallet
wallet_from_mnemonic
Create a wallet from a mnemonic phrase
wallet_from_private_key
Create a wallet from a private key
wallet_get_address
Get the wallet address
wallet_get_balance
Get the balance of the wallet
wallet_get_chain_id
Get the chain ID the wallet is connected to
wallet_get_gas_price
Get the current gas price
wallet_get_private_key
Get the wallet private key (with appropriate security warnings)
wallet_get_public_key
Get the wallet public key
wallet_get_transaction_count
Get the number of transactions sent from this account (nonce)
wallet_populate_transaction
Populate a transaction with missing fields
wallet_provider_set
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_send_transaction
Send a transaction
wallet_sign_message
Sign a message
wallet_sign_transaction
Sign a transaction without sending it
wallet_sign_typed_data
Sign typed data (EIP-712)
wallet_verify_message
Verify a signed message
wallet_verify_typed_data
Verify signed typed data
BEFORE YOU INSTALL
What to know first
Tools you get
35 tools when we connected. wallet_create_mnemonic_phrase and wallet_provider_set (which points the server at an RPC endpoint) are undocumented; wallet_get_mnemonic is documented but not registered.
Requires
- npx on PATH
- Node.js
Where it runs
Both documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 35 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @mcp-dockmaster/mcp-cryptowallet-evmMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"mcp-cryptowallet-evm": {
"command": "npx",
"args": [
"@mcp-dockmaster/mcp-cryptowallet-evm"
]
}
}
}Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"mcp-cryptowallet-evm": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_CRYPTOWALLET_EVM>/build/index.js"
]
}
}
}
