Remote MCP · Endpoint

GameBattle MCP server

No. GameBattle answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://gamebattle.net/mcp

The last check completed an MCP handshake.

Registry name
net.gamebattle/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
624 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
GameBattle (gamebattle.net) Korean esports: public tournaments, games, PC bang venues, guides
Listing
From the official MCP registry (active).
Recent checks of GameBattle
CheckedResultHandshake
9 hours agoHandshake completed624 ms
4 days agoHandshake completed605 ms
14 days agoHandshake completed586 ms
15 days agoHandshake completed616 ms
15 days agoHandshake completed585 ms
17 days agoHandshake completed588 ms
18 days agoHandshake completed602 ms
19 days agoHandshake completed588 ms
20 days agoHandshake completed582 ms
21 days agoHandshake completed579 ms
23 days agoHandshake completed603 ms
26 days agoHandshake completed564 ms
28 days agoHandshake completed570 ms

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

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