Remote MCP · Endpoint

GoCDKeys MCP server

No. GoCDKeys answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gocdkeys.com/agent/mcp

The last check completed an MCP handshake.

Registry name
com.gocdkeys/gocdkeys
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
167 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Game prices across verified stores, with price history and a buy-now-or-wait verdict.
Listing
From the official MCP registry (active).
Recent checks of GoCDKeys
CheckedResultHandshake
1 hour agoHandshake completed167 ms
2 days agoHandshake completed498 ms
4 days agoHandshake completed166 ms
5 days agoHandshake completed197 ms
7 days agoHandshake completed183 ms
8 days agoHandshake completed361 ms
9 days agoHandshake completed192 ms
12 days agoHandshake completed182 ms
13 days agoHandshake completed481 ms
15 days agoHandshake completed191 ms
16 days agoHandshake completed527 ms
17 days agoHandshake completed195 ms
18 days agoHandshake completed271 ms
19 days agoHandshake completed482 ms
20 days agoHandshake completed201 ms
21 days agoHandshake completed171 ms
22 days agoHandshake completed516 ms

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

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