Remote MCP · Endpoint

Sync My Cycle MCP server

No. Sync My Cycle answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/syncmycycle
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
19 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Your likely menstrual cycle phase today and this week, with food and workout ideas.
Listing
From the official MCP registry (active).
Recent checks of Sync My Cycle
CheckedResultHandshake
42 minutes agoHandshake completed19 ms
9 days agoHandshake completed20 ms
10 days agoHandshake completed125 ms
11 days agoHandshake completed34 ms
12 days agoHandshake completed47 ms
14 days agoHandshake completed23 ms
15 days agoHandshake completed27 ms
15 days agoHandshake completed34 ms
17 days agoHandshake completed33 ms
19 days agoHandshake completed21 ms
22 days agoHandshake completed42 ms
24 days agoHandshake completed24 ms
26 days agoHandshake completed29 ms
29 days agoHandshake completed24 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 Sync My Cycle and makes no claim about it beyond what these checks measured.