Plumb Data Exchange
REMOTE · NUMBA2WITCHEESE.TAIL7D8D44.TS.NET:10000
Verified table jobs and RPC-free payment verification (Base/Ethereum). Pay per call via x402.
Available components
Last scanned (18 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +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.
- 21 Oct 26 0
- Tool “prove_xrpl_transaction” rewrote its description, which is the text the model reads security
- 20 Oct 26 +1
- 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 security
- Schema quality: 2003 → 2357 ▼ functional
- New tool “credential_status” functional
- New tool “prove_xrpl_transaction” functional
- “try_verify_payment” added an optional parameter “xrplProof” cosmetic
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 13 Oct 26 +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.
- 12 Oct 26 0
- 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 security
- Schema quality: 146 → 166 ▼ functional
- “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” cosmetic
- 10 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=numba2witcheese.tail7d8d44.ts.net | CN=YE1,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 52a25d9100f660490f02bad88fba7cab8fe |
| SANs: numba2witcheese.tail7d8d44.ts.net | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of numba2witcheese.tail7d8d44.ts.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| ts.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp | Verified | 200 | |
| http (plaintext) | http://numba2witcheese.tail7d8d44.ts.net/pde-mcp | HTTPS enforced | 302 | https://numba2witcheese.tail7d8d44.ts.net/pde-mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_x402_receipt ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | – | – |
| offer | object | – | – |
| receipt | object | yes | – |
| sellerAddress | string | – | – |
| sellerJwk | object | – | – |
No output schema declared.
No examples provided.
convert_to_csv ~62
Convert a table to CSV without changing any value; verified by round-trip. Costs $0.05 USDC (x402).
| Name | Type | Req | Description |
|---|---|---|---|
| table | object | yes | A string table: at most 1000 rows x 32 columns, 65536 characters total |
No output schema declared.
No examples provided.
credential_status ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
No output schema declared.
No examples provided.
deduplicate ~95
Remove duplicate rows by exact key, keeping the first or last, and report conflicting columns per group. Costs $0.05 USDC (x402).
| Name | Type | Req | Description |
|---|---|---|---|
| keep | string | yes | Which duplicate to keep |
| keyColumns | array | yes | Columns that together identify a row (exact string match) |
| table | object | yes | A string table: at most 1000 rows x 32 columns, 65536 characters total |
No output schema declared.
No examples provided.
get_job ~48
Free. Status and (once verified) the result of a paid job, using the accessToken its paid call returned.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| jobId | string | yes | – |
No output schema declared.
No examples provided.
get_verification ~90
Free. Current state of a verification by checkId; re-checks it once its retry or challenge time has passed.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
get_verifications ~101
Free. Up to 50 checks at once (re-checked when due), as rows; format "csv" adds a reconciliation CSV.
| Name | Type | Req | Description |
|---|---|---|---|
| checkIds | array | yes | – |
| 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. |
No output schema declared.
No examples provided.
prove_xrpl_transaction ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | – |
No output schema declared.
No examples provided.
reconcile ~89
Compare two versions of a table by key: rows added, removed and changed (with the changed columns). Costs $0.05 USDC (x402).
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | yes | – |
| before | object | yes | A string table: at most 1000 rows x 32 columns, 65536 characters total |
| keyColumns | array | yes | Columns that together identify a row (exact string match) |
No output schema declared.
No examples provided.
try_verify_payment ~336
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Transaction hash (0x + 64 hex; XRPL: 64 hex) |
| xrplProof | object | – | – |
No output schema declared.
No examples provided.
verify_payment ~504
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Transaction hash (0x + 64 hex; XRPL: 64 hex) |
No output schema declared.
No examples provided.
verify_payments_batch ~183
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
watch_verification ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string | yes | – |
| checkId | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
what_should_i_build ~88
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · numba2witcheese.tail7d8d44.ts.net:10000
claude mcp add --transport http mlcharle518-plumb-data-exchange 'https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp'
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.