Remote MCP · Endpoint

GhostKey — Route Paid APIs with x402 MCP server

No. GhostKey — Route Paid APIs with x402 answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://squeezeos-api.onrender.com/mcp/ghostkey

The last check completed an MCP handshake.

Registry name
com.scriptmasterlabs/ghostkey
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
135 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Find paid APIs, check access policy and price, and route x402 requests. No autonomous spending.
Listing
From the official MCP registry (active).
Recent checks of GhostKey — Route Paid APIs with x402
CheckedResultHandshake
2 hours agoHandshake completed135 ms
1 day agoHandshake completed159 ms
2 days agoHandshake completed141 ms
3 days agoHandshake completed143 ms
4 days agoHandshake completed357 ms
5 days agoHandshake completed173 ms
7 days agoHandshake completed299 ms
9 days agoHandshake completed326 ms
12 days agoHandshake completed215 ms
14 days agoHandshake completed140 ms
16 days agoHandshake completed113 ms
18 days agoHandshake completed269 ms
20 days agoHandshake completed120 ms
22 days agoHandshake completed302 ms
24 days agoHandshake completed264 ms
26 days agoHandshake completed174 ms
27 days agoHandshake completed279 ms
29 days agoHandshake completed309 ms

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

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 GhostKey — Route Paid APIs with x402 and makes no claim about it beyond what these checks measured.