Remote MCP · Endpoint

U.CASH Pay MCP server

No. U.CASH Pay answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.u.cash/

The last check completed an MCP handshake.

Registry name
cash.u/ucash-pay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.01 s
Tools exposed
14 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Pay x402 resources on U.CASH from your own wallet: view the price, pay on-chain, settle by hash.
Listing
From the official MCP registry (active).
Recent checks of U.CASH Pay
CheckedResultHandshake
1 hour agoHandshake completed1.01 s
2 days agoHandshake completed296 ms
5 days agoHandshake completed488 ms
7 days agoHandshake completed281 ms
9 days agoHandshake completed213 ms
11 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed251 ms
15 days agoHandshake completed250 ms
17 days agoHandshake completed340 ms
18 days agoHandshake completed233 ms
20 days agoHandshake completed233 ms
21 days agoHandshake completed662 ms
23 days agoHandshake completed232 ms

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

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 U.CASH Pay and makes no claim about it beyond what these checks measured.