Remote MCP · Endpoint

Plan My Workout MCP server

No. Plan My Workout answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://goodturn-mcp.pages.dev/planmyworkout/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/planmyworkout
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
A workout plan for your goal, level, days and equipment, and how to do any exercise.
Listing
From the official MCP registry (active).
Recent checks of Plan My Workout
CheckedResultHandshake
34 minutes agoHandshake completed52 ms
9 days agoHandshake completed35 ms
10 days agoHandshake completed91 ms
11 days agoHandshake completed50 ms
12 days agoHandshake completed34 ms
14 days agoHandshake completed182 ms
14 days agoHandshake completed29 ms
15 days agoHandshake completed26 ms
17 days agoHandshake completed44 ms
19 days agoHandshake completed38 ms
22 days agoHandshake completed37 ms
24 days agoHandshake completed29 ms
26 days agoHandshake completed53 ms
28 days agoHandshake completed32 ms

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

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