Remote MCP · Endpoint

GPU Finder MCP server

No. GPU Finder answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gpufinder.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.gpufinder/gpufinder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
191 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
GPU prices, observed stock and seven-day availability history. Read-only; free API key.
Listing
From the official MCP registry (active).
Recent checks of GPU Finder
CheckedResultHandshake
2 hours agoHandshake completed191 ms
1 day agoHandshake completed223 ms
2 days agoHandshake completed207 ms
3 days agoHandshake completed232 ms
4 days agoHandshake completed231 ms
5 days agoHandshake completed240 ms
7 days agoHandshake completed221 ms
9 days agoHandshake completed356 ms
12 days agoHandshake completed148 ms
14 days agoHandshake completed206 ms
16 days agoHandshake completed96 ms
18 days agoHandshake completed181 ms
20 days agoHandshake completed184 ms
22 days agoHandshake completed371 ms
24 days agoCredentials required—

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