Remote MCP · Endpoint

Plumb Data Exchange MCP server

No. Plumb Data Exchange answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp

The last check completed an MCP handshake.

Registry name
io.github.Mlcharle518/plumb-data-exchange
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
358 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified table jobs and RPC-free payment verification (Base/Ethereum). Pay per call via x402.
Listing
From the official MCP registry (active).
Recent checks of Plumb Data Exchange
CheckedResultHandshake
1 hour agoHandshake completed358 ms
13 hours agoHandshake completed299 ms
2 days agoHandshake completed553 ms
4 days agoHandshake completed335 ms
6 days agoHandshake completed353 ms
9 days agoHandshake completed369 ms
11 days agoHandshake completed359 ms
13 days agoHandshake completed487 ms
15 days agoHandshake completed1.19 s
17 days agoHandshake completed298 ms
19 days agoHandshake completed379 ms
21 days agoHandshake completed313 ms
23 days agoHandshake completed399 ms
24 days agoHandshake completed878 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Plumb Data Exchange and makes no claim about it beyond what these checks measured.