WalletChan MCP
OfficialRelated Servers
Alternatives to WalletChan MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceEnables AI agents to securely manage a non-custodial wallet with locally encrypted seed phrases, supporting balance checks, local signing, token transfers, swaps, and interactions across 10+ blockchain networks.MIT- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Coinbase wallets, trade assets, interact with DeFi protocols, and query on-chain data through natural language.-

Bink MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform blockchain operations like wallet management, token info, DeFi swaps, cross-chain bridging, and price checking across Ethereum, BNB Chain, and Solana.-- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with BNB Chain, including wallet creation, balance queries, token transfers, swaps via PancakeSwap V3, and price data from Binance Oracle.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to check balances and send transactions across multiple blockchains with automatic spending limit protection and policy enforcement.3MIT
- FlicenseCqualityBmaintenanceEnables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.10036 npm42-
TDQS
Scored across 65 tools
Many tools have overlapping or layered purposes, e.g., send_transaction/send_calls/send_prepared_calls/agent_eoa_send_transaction/agent_eoa_send_calls, veil_deposit_status vs veil_wait_for_deposit, resolve_name vs resolve_names, and separate veil vs agent x402 quote/pay paths. Descriptions help, but an agent must still disambiguate between nearly identical wallet, agent, and Veil execution routes.
Most names use snake_case, but the set mixes verb_noun (get_request_status), noun-only (swap, bridge, sign), and prefixed variants (veil_, agent_, list_, get_, send_). The conventions are readable but not predictable enough for a consistent naming score.
65 tools is an extreme mismatch for a single MCP server, far beyond the typical 3-15 well-scoped range. The surface includes many overlapping variants and layers, making the set difficult to navigate rather than each tool clearly earning its place.
The surface covers a broad domain: wallet signing, transactions, swaps, bridges, agent wallets, delegations, Veil privacy, x402 payments, and protocol integrations. However, notable lifecycle gaps remain, such as onchain delegation revocation, transaction history/update/cancel operations, and explicit approval management.