Transaction Explainer MCP server
dev.changefeed/transaction-explainerchangefeed.devstreamable-httpv0.1.0Scanned
Any Ethereum or Base transaction in plain words, with red flags. Paid per call via x402.
2 tools: 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Transaction Explainer MCP server can do
The Transaction Explainer MCP server is published by changefeed.dev, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Only reads 2Show 2 read-only tools
explain_transactionPlain-words explanation of one Ethereum or Base transaction: a one-line summary (swap, send, approval, bridge, deposit, NFT transfer, failed call), every token and NFT movement wit…No findings
Why it is in this group
- The name "explain_transaction" says "explain": a word for reading.
Description, as the server wrote it Plain-words explanation of one Ethereum or Base transaction: a one-line summary (swap, send, approval, bridge, deposit, NFT transfer, failed call), every token and NFT movement with symbols, the account's net change, approvals (incl. Permit2), protocols touched, and red flags: unlimited or wallet approvals, look-alike tokens, address-poisoning spam, failed calls. Handles smart-account (ERC-4337) and gasless USDC (EIP-3009 / x402) transactions. Costs $0.01 (x402, USDC).
tx_statusFree: status (success, failed, pending), block, confirmations, fee, what kind of transaction it is, and how many red flags it has, without the details.No findings
Why it is in this group
- The name "tx_status" says "status": a word for reading.
Description, as the server wrote it Free: status (success, failed, pending), block, confirmations, fee, what kind of transaction it is, and how many red flags it has, without the details. About 20 calls a minute per client.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:19 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http transaction-explainer https://tx.changefeed.dev/mcpclaude mcp add --transport http transaction-explainer https://tx.changefeed.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__transaction-explainer__tx_status",
"mcp__transaction-explainer__explain_transaction"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as transaction-explainer. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.changefeed/transaction-explainer/verify?hash=f7a7830582f9404b67e80f65c6059bbf3fea0526e908c892c3bbafe93670f72a" | jq -e '.changed == false'Pinned hash f7a7830582f9, from Nov 17, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.changefeed/transaction-explainer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.changefeed/transaction-explainer)Source: MCP Registry. Synced Nov 17, 2026, 19:17 UTC.
Transaction Explainer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Transaction Explainer MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Transaction Explainer MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Transaction Explainer MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Transaction Explainer MCP server have?
- 2 tools: 2 read. tx_status and explain_transaction.
Does the Transaction Explainer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Transaction Explainer MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Transaction Explainer MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.