Remote MCP · Endpoint

Zadely AI Browser Games MCP server

No. Zadely AI Browser Games answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://zadely.com/mcp/

The last check completed an MCP handshake.

Registry name
com.zadely/games
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Search free AI-made browser games by genre, AI tool, engine, and multiplayer.
Listing
From the official MCP registry (active).
Recent checks of Zadely AI Browser Games
CheckedResultHandshake
17 minutes agoHandshake completed160 ms
9 days agoHandshake completed338 ms
9 days agoHandshake completed172 ms
11 days agoHandshake completed172 ms
12 days agoHandshake completed427 ms
13 days agoHandshake completed214 ms
14 days agoHandshake completed141 ms
14 days agoHandshake completed227 ms
16 days agoHandshake completed83 ms
19 days agoHandshake completed575 ms
21 days agoHandshake completed99 ms
24 days agoFailed - the server returned an HTTP error—
26 days agoHandshake completed1.17 s
28 days agoHandshake completed662 ms

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

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