Transaction explainer (x402)
Server Details
Explain an EVM transaction in plain words: transfers, swaps, approvals. x402 per call.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
With a single tool there is no possibility of misselection, and its purpose (decode a transaction by hash into a human-readable explanation) is stated unambiguously. An agent will always know when this is the tool to call.
The name chain_transaction_explain is descriptive snake_case with a domain prefix, but the ordering is noun_noun_verb rather than the more conventional verb_noun. With only one tool there is no pattern to test, so consistency is trivially satisfied rather than demonstrated.
One tool is on the thin side, and the surface is essentially a single fixed operation with no parameters exposed for variation (e.g. batch, raw calldata, or chain selection as separate entry points). It is nonetheless coherent — the server's purpose is exactly one decode operation, so the count is defensible but borderline.
For a single-transaction explainer the coverage is solid (actors, full asset deltas, status, fee, decoded method, multi-chain), but there are notable gaps: no batch decoding, no raw-calldata/input decoding, and no companion lookup for addresses or token metadata. Agents needing anything beyond one hash-in, explanation-out will hit a dead end.
Available Tools
1 toolchain_transaction_explainARead-onlyIdempotentInspect
$0.005 via x402: decode any transaction by hash into a plain-English explanation — what actually happened (a swap, transfer, approval, mint, or contract call), who the actors are, and the full list of asset changes (every native coin and token in/out with symbol, amount and direction), plus status, fee and the decoded method. The read agents make to UNDERSTAND a tx, not just confirm it landed: for wallet UX, accounting, risk, dispute and trading agents. Across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. Live from Blockscout; one paid call instead of running your own indexer + ABI decoder.
Inputs: hash (required), chain, x_payment.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Any Ethereum or Base transaction in plain words, with red flags. Paid per call via x402.
Decode Base txs: plain English, strict JSON, risk flags, no LLM. 50 free/24h per IPv4 or /64, $0.02.
x402 pay-per-call: EVM balances, tx decode, transfers; AI extract, classify, embed, speech, image
Pay-per-call tx explainer, DeFi yields, token safety, SEC 8-K and OFAC data via x402 (USDC on Base).
Related MCP Servers
- AlicenseAqualityCmaintenanceDecodes Ethereum calldata and returns a safety verdict with plain-English explanations of what the transaction does, flagging dangerous actions like unlimited approvals or gasless permits.2MIT
- AlicenseAqualityDmaintenanceDecodes raw EVM bytes into human-readable JSON via tools for logs, calldata, selectors, and ABIs across multiple chains. Read-only, keyless, and stateless, with optional x402 payment settlement.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents and humans to pay per question over x402 and receive plain-language answers about on-chain activity, priced by complexity before execution. Each paid request runs a live subgraph round trip to search, validate, generate and execute a GraphQL query, then synthesizes the raw results into a grounded response alongside the underlying data.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to turn raw calldata, transaction objects, JSON-RPC requests, EIP-712 typed data and personal_sign messages into short plain-English briefings covering what a request asks for, which risky allowances or permissions need attention, and what could not be verified. Runs entirely offline with no RPC, wallet, API key or safety verdict, using three read-only tools exposed to any MCP client.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.