Remote MCP · Endpoint

AmpleRun GPU rentals MCP server

No. AmpleRun GPU rentals answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://amplerun.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.amplerun/gpu-rentals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
781 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find, price, rent and stop GPUs on AmpleRun. Paid in USDC or USDT on Base. Flat 5% fee.
Listing
From the official MCP registry (active).
Recent checks of AmpleRun GPU rentals
CheckedResultHandshake
1 hour agoHandshake completed781 ms
2 days agoHandshake completed496 ms
4 days agoHandshake completed697 ms
6 days agoHandshake completed281 ms
8 days agoHandshake completed495 ms
10 days agoHandshake completed269 ms
12 days agoHandshake completed392 ms
14 days agoHandshake completed258 ms
15 days agoHandshake completed287 ms
17 days agoHandshake completed430 ms
18 days agoHandshake completed284 ms
20 days agoHandshake completed478 ms
22 days agoHandshake completed511 ms
24 days agoHandshake completed475 ms

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

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