Remote MCP · Endpoint

FoolFish Games MCP server

No. FoolFish Games answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://foolfishgames.com/mcp

The last check completed an MCP handshake.

Registry name
com.foolfishgames/games
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.51 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find free browser games, get recommendations, and read gameplay guides from FoolFish Games.
Listing
From the official MCP registry (active).
Recent checks of FoolFish Games
CheckedResultHandshake
3 hours agoHandshake completed1.51 s
9 days agoHandshake completed490 ms
10 days agoHandshake completed509 ms
11 days agoHandshake completed464 ms
12 days agoHandshake completed475 ms
14 days agoHandshake completed469 ms
14 days agoHandshake completed481 ms
15 days agoHandshake completed499 ms
17 days agoHandshake completed479 ms
19 days agoHandshake completed466 ms
21 days agoHandshake completed475 ms
24 days agoHandshake completed469 ms
26 days agoHandshake completed509 ms
28 days agoHandshake completed502 ms

The last 14 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 FoolFish Games and makes no claim about it beyond what these checks measured.