Remote MCP · Endpoint

PaidHandshake Exchange MCP server

No. PaidHandshake Exchange answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

https://paidhandshake.com/mcp

The last check completed an MCP handshake.

Registry name
com.paidhandshake/exchange
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
396 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified agent commerce plus worker-published structured intelligence and machine payments.
Listing
From the official MCP registry (active).
Recent checks of PaidHandshake Exchange
CheckedResultHandshake
55 minutes agoHandshake completed396 ms
1 day agoHandshake completed421 ms
4 days agoHandshake completed302 ms
7 days agoHandshake completed1.42 s
9 days agoHandshake completed443 ms
11 days agoHandshake completed381 ms
13 days agoHandshake completed320 ms
15 days agoHandshake completed207 ms
17 days agoHandshake completed550 ms
19 days agoHandshake completed218 ms
21 days agoHandshake completed179 ms
22 days agoHandshake completed241 ms
23 days agoHandshake completed222 ms
24 days agoHandshake completed239 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 PaidHandshake Exchange and makes no claim about it beyond what these checks measured.