Remote MCP · Endpoint

GameDev.net MCP server

No. GameDev.net answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gamedev.net/mcp/

The last check completed an MCP handshake.

Registry name
net.gamedev/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
209 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and cite GameDev.net forums, tutorials, postmortems, and game-industry news.
Listing
From the official MCP registry (active).
Recent checks of GameDev.net
CheckedResultHandshake
1 hour agoHandshake completed209 ms
2 days agoHandshake completed245 ms
4 days agoHandshake completed147 ms
5 days agoHandshake completed268 ms
7 days agoHandshake completed127 ms
8 days agoHandshake completed143 ms
9 days agoHandshake completed177 ms
12 days agoHandshake completed98 ms
13 days agoHandshake completed122 ms
15 days agoHandshake completed112 ms
17 days agoHandshake completed105 ms
18 days agoHandshake completed120 ms
19 days agoHandshake completed102 ms
20 days agoHandshake completed180 ms
21 days agoHandshake completed112 ms
21 days agoHandshake completed133 ms
23 days agoHandshake completed231 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 GameDev.net and makes no claim about it beyond what these checks measured.