Remote MCP · Endpoint

Rozo Checkout MCP server

No. Rozo Checkout answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.rozo.ai/mcp?src=registry

The last check completed an MCP handshake.

Registry name
io.github.RozoAI/checkout
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Pay OpenRouter and Coinbase payment links with USDC, USDT, ETH, BNB, POL, SOL or BTC Lightning.
Listing
From the official MCP registry (active).
Recent checks of Rozo Checkout
CheckedResultHandshake
7 hours agoHandshake completed159 ms
4 days agoHandshake completed157 ms
14 days agoHandshake completed143 ms
15 days agoHandshake completed161 ms
15 days agoHandshake completed184 ms
17 days agoHandshake completed221 ms
18 days agoHandshake completed239 ms
19 days agoHandshake completed202 ms
20 days agoHandshake completed205 ms
21 days agoHandshake completed165 ms
23 days agoHandshake completed117 ms
26 days agoHandshake completed156 ms
28 days agoHandshake completed205 ms

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

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