Remote MCP · Endpoint

Edgegap MCP server

No. Edgegap answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.edgegap.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.edgegap/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Deploy and operate multiplayer game servers on Edgegap's global edge network.
Listing
From the official MCP registry (active).
Recent checks of Edgegap
CheckedResultHandshake
1 hour agoHandshake completed86 ms
2 days agoHandshake completed250 ms
4 days agoHandshake completed178 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed188 ms
8 days agoHandshake completed411 ms
9 days agoHandshake completed216 ms
12 days agoHandshake completed167 ms
13 days agoHandshake completed217 ms
15 days agoHandshake completed160 ms
16 days agoHandshake completed75 ms
18 days agoHandshake completed146 ms
19 days agoHandshake completed42 ms
20 days agoHandshake completed151 ms
20 days agoHandshake completed40 ms
21 days agoHandshake completed213 ms
22 days agoHandshake completed394 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 Edgegap and makes no claim about it beyond what these checks measured.