Remote MCP · Endpoint

Foundplay for creators MCP server

No. Foundplay for creators answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://foundplay.io/mcp/creators

The last check completed an MCP handshake.

Registry name
io.foundplay/creators
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
237 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
For browser game makers: check a game, free listing link, Boost plans, checkout links. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Foundplay for creators
CheckedResultHandshake
18 minutes agoHandshake completed237 ms
10 days agoHandshake completed173 ms
10 days agoHandshake completed172 ms
11 days agoHandshake completed159 ms
13 days agoHandshake completed140 ms
14 days agoHandshake completed166 ms
14 days agoHandshake completed140 ms
15 days agoHandshake completed147 ms
17 days agoHandshake completed333 ms
19 days agoHandshake completed4.57 s
21 days agoHandshake completed151 ms
24 days agoHandshake completed127 ms
26 days agoHandshake completed151 ms
28 days agoHandshake completed164 ms

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

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