Remote MCP · Endpoint

Rack Rates MCP server

No. Rack Rates answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://rackrates.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.rackrates/ledger
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.35 s
Tools exposed
13 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Published list prices of compute (VPS, GPU hours, LLM tokens, media), archived daily. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Rack Rates
CheckedResultHandshake
37 minutes agoHandshake completed2.35 s
4 days agoHandshake completed694 ms
7 days agoHandshake completed708 ms
16 days agoHandshake completed700 ms
16 days agoHandshake completed724 ms
18 days agoHandshake completed704 ms
19 days agoHandshake completed726 ms
20 days agoHandshake completed773 ms
21 days agoHandshake completed758 ms
22 days agoHandshake completed724 ms
23 days agoHandshake completed697 ms
26 days agoHandshake completed764 ms
29 days agoHandshake completed370 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Rack Rates and makes no claim about it beyond what these checks measured.