# Transaction Explainer (remote · tx.changefeed.dev)

Any Ethereum or Base transaction in plain words, with red flags. Paid per call via x402.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tx.changefeed.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/dev-changefeed-transaction-explainer/tx.md), [page](https://verifymcp.io/servers/dev-changefeed-transaction-explainer/tx)

## Channel facts

- Endpoint: `https://tx.changefeed.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 368 tokens (~184/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Transaction Explainer MCP server?

Transaction Explainer is a hosted endpoint at https://tx.changefeed.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-changefeed-transaction-explainer 'https://tx.changefeed.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-changefeed-transaction-explainer": {
      "url": "https://tx.changefeed.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-changefeed-transaction-explainer": {
      "type": "http",
      "url": "https://tx.changefeed.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-changefeed-transaction-explainer]
url = "https://tx.changefeed.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-changefeed-transaction-explainer": {
      "type": "remote",
      "url": "https://tx.changefeed.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-changefeed-transaction-explainer --url 'https://tx.changefeed.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-changefeed-transaction-explainer:
    url: "https://tx.changefeed.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-changefeed-transaction-explainer": {
      "Transport": "http",
      "Url": "https://tx.changefeed.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-changefeed-transaction-explainer -t streamable-http -u 'https://tx.changefeed.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-changefeed-transaction-explainer": {
      "type": "http",
      "url": "https://tx.changefeed.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 59)

First indexed and scored.

## MCP tools (2)

### `tx_status` (~83 tokens)

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.

Input parameters:

- `chain` (string, required): Chain: ethereum, base
- `hash` (string, required): Transaction hash, 0x followed by 64 hex characters

### `explain_transaction` (~156 tokens)

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).

Input parameters:

- `chain` (string, required): Chain: ethereum, base
- `hash` (string, required): Transaction hash, 0x followed by 64 hex characters

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-changefeed-transaction-explainer/tx#diagnostics

## Score history

- 2026-11-21: 61
- 2026-11-20: 60
- 2026-11-19: 60
- 2026-11-18: 59
- 2026-11-17: 59

## Common questions

### What is the Transaction Explainer MCP server?

Transaction Explainer is an MCP server listed in the public MCP registry as dev.changefeed/transaction-explainer. Any Ethereum or Base transaction in plain words, with red flags. Paid per call via x402. This page covers its hosted endpoint (https://tx.changefeed.dev/mcp).

### Is the Transaction Explainer MCP server safe to use?

Transaction Explainer scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Transaction Explainer MCP server expose?

Transaction Explainer exposes 2 tools: tx_status, explain_transaction. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.

### Does the Transaction Explainer MCP server require authentication?

No. We connected to Transaction Explainer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Transaction Explainer MCP server still maintained?

Transaction Explainer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Transaction Explainer MCP server?

VerifyMCP ran 11 checks on Transaction Explainer, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Transaction Explainer: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tx.changefeed.dev/mcp
- Website: https://tx.changefeed.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-changefeed-transaction-explainer/tx.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-changefeed-transaction-explainer/tx/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-changefeed-transaction-explainer/tx.json
- HTML version of this page: https://verifymcp.io/servers/dev-changefeed-transaction-explainer/tx
