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.
An EVM wallet server: wallet construction and signing on one side, provider and network reads on the other.
- 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.
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.
One command — npx @mcp-dockmaster/mcp-cryptowallet-evm