Remote MCP · Endpoint

GymFlexa Gym Management MCP server

No. GymFlexa Gym Management answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://mcp.gymflexa.com/mcp

The last check completed an MCP handshake.

Registry name
com.gymflexa/gymflexa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
382 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
See your gym's open slots, services, how busy each day is and your payment totals.
Listing
From the official MCP registry (active).
Recent checks of GymFlexa Gym Management
CheckedResultHandshake
59 minutes agoHandshake completed382 ms
9 days agoHandshake completed374 ms
10 days agoHandshake completed240 ms
11 days agoHandshake completed137 ms
12 days agoHandshake completed168 ms
14 days agoHandshake completed69 ms
14 days agoHandshake completed142 ms
15 days agoHandshake completed142 ms
17 days agoHandshake completed350 ms
19 days agoHandshake completed131 ms
21 days agoHandshake completed111 ms
24 days agoHandshake completed95 ms
26 days agoHandshake completed107 ms
28 days agoHandshake completed130 ms

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

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