A
licenseNot graded
qualityA
maintenanceMCP 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.
1
MIT
eth-mcp
Related Servers
Alternatives to eth-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to simulate EVM bytecode and probe capabilities, serving as a gateway to an Ethereum execution engine.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server providing tools for AI agents to mint ERC-20 tokens across multiple blockchains.2 npm22MIT
multivon-mcpofficial
AlicenseAqualityAmaintenanceMCP server that gives AI coding agents direct access to evaluation tools.23Apache 2.0- AlicenseAqualityBmaintenanceAn MCP server that gives autonomous coding agents deterministic, schema-validated tools for EVM smart contract development — security scanning, gas profiling, compiler diagnostics, and transaction simulation.91MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents real-time access to DeFi across multiple chains, enabling non-custodial crypto trading, portfolio queries, and transaction execution.07MIT
TDQS
A3.9/5.0
Scored across 34 tools
Disambiguation5/5
Each tool clearly targets a distinct aspect of the scafford-eth workflow, education, DeFi data, or address lookups. Even similar-sounding tools like addresses_getToken and addresses_findToken have different purposes (exact address vs. cross-chain search), eliminating confusion.
Naming Consistency5/5
All tool names follow a consistent 'category_verb_noun' pattern using snake_case (e.g., education_explainLesson, stack_start, defi_getProtocolTVL). This makes the tool surface highly predictable and easy for an AI to navigate.
Tool Count4/5
34 tools is on the high side, but each tool serves a necessary function within the multi-faceted scaffold-eth domain (stack management, education, DeFi, addresses, frontend, project files, processes). A few tools could be merged (e.g., stack_start could combine fork/deploy/frontend into one param), but the granularity aids clarity.
Completeness4/5
The tool set covers the full local development workflow: init, install, start/stop components, configure external contracts, check production readiness, and even education and linting. The only notable gap is automated mainnet deployment, which is intentionally left as manual instructions, so the surface feels slightly incomplete for a truly end-to-end pipeline.
Maintenance
ActivityInactive
ResponsivenessNo issues