transaction-mcp-server
transaction-mcp-server is an offline Ethereum wallet/transaction MCP server that exposes tools to build, encode/decode, hash, and sign Ethereum transactions (legacy/Type 0, access-list/Type 1, EIP-1559/Type 2), plus related helpers like calldata parsing and transaction validation. It runs as a standalone Python package and is designed to be used by AI assistants via the Model Context Protocol (MCP).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Strengths (from README): designed for offline/no network calls; keys are passed through and not persisted; uses widely used Ethereum cryptographic primitives/libraries. Concerns: no explicit discussion of how secrets are handled in logs/memory beyond a warning; no stated policy for input validation failures or misuse; auth model is effectively “none” because sensitive material is provided directly by the caller.
⚡ Reliability
Best When
You need deterministic, offline transaction build/sign/encode/decode functionality exposed as MCP tools to an AI agent (e.g., for air-gapped or no-network environments).
Avoid When
You need a hosted API with authentication, audit logging, or managed key custody; or you require explicit guarantees about gas-price “current” estimates (the docs only mention estimate_gas, without describing data sources).
Use Cases
- • Agent-assisted offline construction of unsigned transactions
- • Signing transactions from provided private keys without any network calls
- • RLP encoding/decoding and wire-format serialization for transactions
- • EIP-1559/legacy/access-list transaction preparation and hashing
- • Pre-signing analysis (transaction hash calculation) and validation
Not For
- • Submitting transactions to the blockchain (no networking is described)
- • Custody/long-term key storage (keys are described as passed through and not persisted)
- • Production key management and signing workflows that require hardened operational controls beyond offline crypto tooling
Interface
Authentication
No network authentication is described. The primary sensitive input is private key material provided to tools at call time.
Pricing
No pricing information provided; appears to be open-source tooling under MIT.
Agent Metadata
Known Gotchas
- ⚠ Be careful to pass correct chain_id/nonce/gas parameters; wrong inputs can produce invalid or unintended transactions.
- ⚠ If tools accept private keys, ensure the agent/user does not log or persist them; the README warns that tools handle sensitive cryptographic material.
- ⚠ Offline operation means tools likely won’t fetch network state (e.g., gas price); provide required parameters explicitly.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for transaction-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.