ethereum-wallet-mcp
Related Servers
Alternatives to ethereum-wallet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server for batch-generating wallets compatible with Ethereum and all EVM-compatible chains.11MIT
- AlicenseCqualityCmaintenanceSelf-hosted wallet MCP server for AI agents. Provides 42 tools for multi-chain crypto operations: transfers, token management, DeFi (swap, lend, stake, bridge, perp), NFT, smart contracts, and x402 payments. Supports EVM and Solana with policy engine, spending limits, and human approval.6029MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.1MIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server enabling AI agents to manage EVM wallets, check balances, swap tokens, and securely execute transactions via 1Claw Intents without exposing private keys.50 PyPIMIT
- AlicenseNot gradedqualityFmaintenanceA lightweight, fast MCP server that provides onchain capabilities for the LLMs and Agents.62 npm255MIT
- AlicenseNot gradedqualityBmaintenanceMulti-chain wallet MCP server that enables AI agents to manage Bitcoin, Ethereum, Solana, and Tron wallets via tools for addresses, balances, transactions, and token operations.223 npmCC BY-4.0
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.