# Plumb Data Exchange (remote · numba2witcheese.tail7d8d44.ts.net:10000)

Verified table jobs and RPC-free payment verification (Base/Ethereum). Pay per call via x402.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `numba2witcheese.tail7d8d44.ts.net:10000`: 66/100 (this document), [markdown](https://verifymcp.io/servers/mlcharle518-plumb-data-exchange/pde-mcp.md), [page](https://verifymcp.io/servers/mlcharle518-plumb-data-exchange/pde-mcp)

## Channel facts

- Endpoint: `https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-10-22.

- **Endpoint Security**: 57/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 14 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 is enforced; there's no plaintext access path.
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2314 tokens (~165/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deduplicate" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 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 Plumb Data Exchange MCP server?

Plumb Data Exchange is a hosted endpoint at https://numba2witcheese.tail7d8d44.ts.net:10000/pde-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 mlcharle518-plumb-data-exchange 'https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mlcharle518-plumb-data-exchange": {
      "url": "https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mlcharle518-plumb-data-exchange": {
      "type": "http",
      "url": "https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mlcharle518-plumb-data-exchange]
url = "https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mlcharle518-plumb-data-exchange": {
      "type": "remote",
      "url": "https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mlcharle518-plumb-data-exchange --url 'https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mlcharle518-plumb-data-exchange:
    url: "https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mlcharle518-plumb-data-exchange": {
      "Transport": "http",
      "Url": "https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mlcharle518-plumb-data-exchange -t streamable-http -u 'https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp'
```

### Other

```json
{
  "mcpServers": {
    "mlcharle518-plumb-data-exchange": {
      "type": "http",
      "url": "https://numba2witcheese.tail7d8d44.ts.net:10000/pde-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-10-22 (score 66, +1)

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

### 2026-10-21 (score 65, 0)

- [security] Tool “prove_xrpl_transaction” rewrote its description, which is the text the model reads

### 2026-10-20 (score 65, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “try_verify_payment” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2003 → 2357
- [functional] New tool “credential_status”
- [functional] New tool “prove_xrpl_transaction”
- [cosmetic] “try_verify_payment” added an optional parameter “xrplProof”

### 2026-10-18 (score 64, +1)

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

### 2026-10-16 (score 63, +1)

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

### 2026-10-13 (score 62, +1)

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

### 2026-10-12 (score 61, 0)

- [security] Tool “verify_payment” rewrote its description, which is the text the model reads
- [security] Tool “verify_payments_batch” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 146 → 166
- [cosmetic] “try_verify_payment” added an optional parameter “invoiceId”
- [cosmetic] “verify_payment” added an optional parameter “invoiceId”
- [cosmetic] “get_verification” reworded the description of “requiredLevel”
- [cosmetic] “get_verifications” reworded the description of “requiredLevel”
- [cosmetic] “try_verify_payment” reworded the description of “minAmountRaw”
- [cosmetic] “try_verify_payment” reworded the description of “payee”
- [cosmetic] “try_verify_payment” reworded the description of “requiredLevel”
- [cosmetic] “try_verify_payment” reworded the description of “token”
- [cosmetic] “try_verify_payment” reworded the description of “txHash”
- [cosmetic] “verify_payment” reworded the description of “minAmountRaw”
- [cosmetic] “verify_payment” reworded the description of “payee”
- [cosmetic] “verify_payment” reworded the description of “requiredLevel”
- [cosmetic] “verify_payment” reworded the description of “token”
- [cosmetic] “verify_payment” reworded the description of “txHash”
- [cosmetic] “verify_payments_batch” reworded the description of “requiredLevel”
- [cosmetic] “watch_verification” reworded the description of “requiredLevel”

### 2026-10-10 (score 61)

First indexed and scored.

## MCP tools (14)

### `convert_to_csv` (~62 tokens)

Convert a table to CSV without changing any value; verified by round-trip. Costs $0.05 USDC (x402).

Input parameters:

- `table` (object, required): A string table: at most 1000 rows x 32 columns, 65536 characters total

### `deduplicate` (~95 tokens)

Remove duplicate rows by exact key, keeping the first or last, and report conflicting columns per group. Costs $0.05 USDC (x402).

Input parameters:

- `keep` (string, required): Which duplicate to keep
- `keyColumns` (array, required): Columns that together identify a row (exact string match)
- `table` (object, required): A string table: at most 1000 rows x 32 columns, 65536 characters total

### `reconcile` (~89 tokens)

Compare two versions of a table by key: rows added, removed and changed (with the changed columns). Costs $0.05 USDC (x402).

Input parameters:

- `after` (required)
- `before` (object, required): A string table: at most 1000 rows x 32 columns, 65536 characters total
- `keyColumns` (array, required): Columns that together identify a row (exact string match)

### `verify_payment` (~504 tokens)

Verify an on-chain payment without trusting any RPC: did this tx transfer at least this amount of a token (default USDC) to this payee, optionally from this payer? Proven by Plumb (Base via proof-backed L1 checkpoints, Ethereum via a light client, XRP Ledger via a quorum of Ripple's validator list: RLUSD, XRP or any issued currency). Bound to the exact transfer (log index); returns the proof level, how long a Base checkpoint can still be challenged, the evidence to re-check, and an Ed25519-signed receipt. Never answers not_paid while a payment is still pending; abstains (unverifiable) whenever the proof is incomplete. Costs $0.02 USDC (x402) ($0.002 for an XRP Ledger payment); asking again about the same claim costs nothing. Optional requiredLevel (releasable or not) and callbackUrl (signed events when the level is reached, the answer changes, or checking gives up).

Input parameters:

- `callbackUrl` (string): https URL to notify (signed, retried) when requiredLevel is reached, when the answer changes, or when checking gives up
- `chain` (string): Chain of the payment
- `invoiceId` (string): XRPL only: the InvoiceID (64 hex) the payment must carry; binds the answer and its signed receipt to your invoice
- `logIndex` (integer): Bind to one transfer: its position within the tx's logs
- `minAmountRaw` (string): Minimum amount in base units, e.g. "50000" = 0.05 USDC (default: any). XRPL: XRP drops, or millionths of an issued currency
- `payee` (string, required): Address that should have received the money (XRPL: an r... account)
- `payer` (string): Only count transfers from this address (the token holder who paid)
- `requiredLevel` (string): Proof level you need before releasing money (Base: tee_attested < zk_proven < resolved; Ethereum: finalized; XRPL: unl_quorum). The answer then says whether it is releasable.
- `token` (string): ERC-20 contract (default: USDC on the chain). XRPL: RLUSD (default), XRP, or CURRENCY.rIssuer
- `txHash` (string, required): Transaction hash (0x + 64 hex; XRPL: 64 hex)

### `try_verify_payment` (~336 tokens)

Free: the same verification as verify_payment, limited to 3 NEW claims per client per day (asking again about a claim already checked is always free). Holders of the exchange's on-ledger ProvenPayer credential get more: pass xrplProof (see credential_status).

Input parameters:

- `chain` (string): Chain of the payment
- `invoiceId` (string): XRPL only: the InvoiceID (64 hex) the payment must carry; binds the answer and its signed receipt to your invoice
- `logIndex` (integer): Bind to one transfer: its position within the tx's logs
- `minAmountRaw` (string): Minimum amount in base units, e.g. "50000" = 0.05 USDC (default: any). XRPL: XRP drops, or millionths of an issued currency
- `payee` (string, required): Address that should have received the money (XRPL: an r... account)
- `payer` (string): Only count transfers from this address (the token holder who paid)
- `requiredLevel` (string): Proof level you need before releasing money (Base: tee_attested < zk_proven < resolved; Ethereum: finalized; XRPL: unl_quorum). The answer then says whether it is releasable.
- `token` (string): ERC-20 contract (default: USDC on the chain). XRPL: RLUSD (default), XRP, or CURRENCY.rIssuer
- `txHash` (string, required): Transaction hash (0x + 64 hex; XRPL: 64 hex)
- `xrplProof` (object)

### `get_verification` (~90 tokens)

Free. Current state of a verification by checkId; re-checks it once its retry or challenge time has passed.

Input parameters:

- `checkId` (string, required)
- `requiredLevel` (string): Proof level you need before releasing money (Base: tee_attested < zk_proven < resolved; Ethereum: finalized; XRPL: unl_quorum). The answer then says whether it is releasable.

### `watch_verification` (~122 tokens)

Free for a PAID check: add a callback (https) that receives signed events when requiredLevel is reached, when the answer changes, when it becomes final, or when checking gives up. The service re-checks on its own.

Input parameters:

- `callbackUrl` (string, required)
- `checkId` (string, required)
- `requiredLevel` (string): Proof level you need before releasing money (Base: tee_attested < zk_proven < resolved; Ethereum: finalized; XRPL: unl_quorum). The answer then says whether it is releasable.

### `verify_payments_batch` (~183 tokens)

Verify up to 25 payments in one call for $0.25 ($0.05 when every claim is on the XRP Ledger) USDC (x402): give `claims` (same fields as verify_payment) or `csv` (header: chain,txHash,payee,token,minAmountRaw,payer,logIndex,invoiceId). Claims already checked cost nothing; if all of them were, nothing is charged. Returns one row per claim (format "csv" adds a reconciliation CSV).

Input parameters:

- `claims` (array)
- `csv` (string)
- `format` (string)
- `requiredLevel` (string): Proof level you need before releasing money (Base: tee_attested < zk_proven < resolved; Ethereum: finalized; XRPL: unl_quorum). The answer then says whether it is releasable.

### `get_verifications` (~101 tokens)

Free. Up to 50 checks at once (re-checked when due), as rows; format "csv" adds a reconciliation CSV.

Input parameters:

- `checkIds` (array, required)
- `format` (string)
- `requiredLevel` (string): Proof level you need before releasing money (Base: tee_attested < zk_proven < resolved; Ethereum: finalized; XRPL: unl_quorum). The answer then says whether it is releasable.

### `check_x402_receipt` (~130 tokens)

Free. Cross-check a seller's signed x402 offer + receipt (offer-and-receipt extension): verifies the signatures (official x402 functions; pin the seller with sellerAddress for EIP-712 or sellerJwk for JWS), checks offer and receipt agree, and returns the exact `claim` to prove with verify_payment. Pass that verification's checkId to learn which side failed.

Input parameters:

- `checkId` (string)
- `offer` (object)
- `receipt` (object, required)
- `sellerAddress` (string)
- `sellerJwk` (object)

### `what_should_i_build` (~88 tokens)

What should I build? x402 agent demand by category from public chain data (Base USDC + XRPL), with fake demand removed (testers, sellers paying themselves, loops; wallet fleets counted as one buyer) and gaps ranked (repeat buyers per seller). Rolling 7 days, refreshed every 2 h. Signed answer with sample transactions you can check, plus a dashboard link.

### `credential_status` (~100 tokens)

Free. The exchange's on-ledger ProvenPayer credential (XLS-70): issued to an XRPL account after 2 settled, Plumb-proven payments to the house; readable by any seller with ledger_entry. Returns the account's standing, the issued credential (with the CredentialCreate hash, provable with plumb-xrpl), how to accept it, and the challenge format for the holder unlock.

Input parameters:

- `account` (string)

### `prove_xrpl_transaction` (~74 tokens)

Prove any XRP Ledger transaction without trusting a server: validator-list quorum, hash links, rebuilt tx tree. Returns full fields, metadata (balances, escrows, channels, credentials as of the tx), quorum evidence and a signed receipt. Unvalidated tx keeps your payment.

Input parameters:

- `txHash` (string, required)

### `get_job` (~48 tokens)

Free. Status and (once verified) the result of a paid job, using the accessToken its paid call returned.

Input parameters:

- `accessToken` (string, required)
- `jobId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mlcharle518-plumb-data-exchange/pde-mcp#diagnostics

## Score history

- 2026-10-22: 66
- 2026-10-21: 65
- 2026-10-20: 65
- 2026-10-19: 64
- 2026-10-18: 64
- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 62
- 2026-10-12: 61
- 2026-10-10: 61

## Common questions

### What is the Plumb Data Exchange MCP server?

Plumb Data Exchange is an MCP server listed in the public MCP registry as io.github.Mlcharle518/plumb-data-exchange. Verified table jobs and RPC-free payment verification (Base/Ethereum). Pay per call via x402. This page covers its hosted endpoint (https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp).

### Is the Plumb Data Exchange MCP server safe to use?

Plumb Data Exchange scores 66 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 Plumb Data Exchange MCP server expose?

Plumb Data Exchange exposes 14 tools: convert_to_csv, deduplicate, reconcile, verify_payment, try_verify_payment, and 9 more. Their descriptions and schemas cost roughly 2,022 tokens of context every time the server is loaded.

### Does the Plumb Data Exchange MCP server require authentication?

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

### Is the Plumb Data Exchange MCP server still maintained?

Plumb Data Exchange is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp
- Website: https://numba2witcheese.tail7d8d44.ts.net:10000/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mlcharle518-plumb-data-exchange/pde-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mlcharle518-plumb-data-exchange/pde-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mlcharle518-plumb-data-exchange/pde-mcp