Remote MCP · Endpoint

org.sky-1/rate-hub MCP server

No. org.sky-1/rate-hub answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://x402-v1.sky-1.org/mcp

The last check completed an MCP handshake.

Registry name
org.sky-1/rate-hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
775 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Indicative fiat and crypto rates over MCP, paid per request via x402 at $0.0001/request.
Listing
From the official MCP registry (active).
Recent checks of org.sky-1/rate-hub
CheckedResultHandshake
2 hours agoHandshake completed775 ms
1 day agoHandshake completed500 ms
2 days agoHandshake completed486 ms
3 days agoHandshake completed492 ms
4 days agoHandshake completed511 ms
5 days agoHandshake completed526 ms
7 days agoHandshake completed560 ms
10 days agoHandshake completed535 ms
12 days agoHandshake completed512 ms
14 days agoHandshake completed470 ms
17 days agoHandshake completed489 ms
19 days agoHandshake completed628 ms
21 days agoHandshake completed501 ms
23 days agoHandshake completed572 ms
25 days agoHandshake completed474 ms

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

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 org.sky-1/rate-hub and makes no claim about it beyond what these checks measured.