etherscan-mcp-server
Provides a Model Context Protocol (MCP) server (Go) that wraps the Etherscan API V2 to let LLM applications query multi-chain blockchain data such as balances, blocks, transactions, contract ABI/source, gas oracle, and token/NFT transfers.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The README indicates the server uses an Etherscan API key provided via environment variable, but does not document transport security for the SSE endpoint (only an example uses http://localhost). It also does not describe whether requests to the MCP server require authentication, how logs redact secrets, or how tool inputs are validated. Dependency/security hygiene and vulnerability posture cannot be confirmed from the provided content.
⚡ Reliability
Best When
When you want an MCP-compatible interface to Etherscan API data so an LLM agent can call structured tools to fetch blockchain information.
Avoid When
When you need an audited, fully specified API contract for error codes, rate limits, pagination, and idempotency behavior, or when you require advanced security controls beyond an environment-provided API key.
Use Cases
- • Building LLM tools/agents that answer blockchain data questions from user prompts
- • Retrieving account balances, token balances, and recent transfers across many EVM-compatible chains
- • Fetching block/transaction details and transaction status/receipts
- • Looking up verified contract ABI and source code for on-chain addresses
- • Getting gas price oracle data and latest block number for network-aware agents
Not For
- • Writing/creating transactions on-chain (it appears focused on read-only data retrieval and contract read methods)
- • Use cases requiring strong contractual guarantees (no SLA or uptime/release stability info provided)
- • Environments where API key exposure risk or weak logging practices cannot be reviewed
Interface
Authentication
Only an API key is mentioned. No OAuth, scopes, or per-tool authorization model is documented in the provided README.
Pricing
Pricing is not described for the MCP server itself; it relies on Etherscan API usage. Costs depend on the Etherscan plan and request volume.
Agent Metadata
Known Gotchas
- ⚠ Etherscan rate limits and transient API failures may affect tool calls; README does not describe retry/backoff behavior.
- ⚠ Contract-related tools depend on verified contracts; unverified contracts may fail or return empty results (not documented).
- ⚠ SSE mode exposes an HTTP SSE endpoint; ensure network access and auth boundaries are appropriate (auth for the MCP server is not documented).
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for etherscan-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.