Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sync My Cycle

REMOTE · GOODTURN-MCP.PAGES.DEV

Your likely menstrual cycle phase today and this week, with food and workout ideas.

0 this week 83 Trust /100

Last scanned (14 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1018 tokens (~339/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://goodturn-mcp.pages.dev/syncmycycle/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=goodturn-mcp.pages.dev CN=YE1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 590c8ade87714dff31f31ce636eafc7da48
SANs: *.goodturn-mcp.pages.dev, goodturn-mcp.pages.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of goodturn-mcp.pages.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
pages.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://goodturn-mcp.pages.dev/syncmycycle/mcp Verified 200
http (plaintext) http://goodturn-mcp.pages.dev/syncmycycle/mcp HTTPS enforced 301 https://goodturn-mcp.pages.dev/syncmycycle/mcp
MCP tools · 3 exposed · ~856 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_todays_phase ~408

Today's cycle phase, with workout and food ideas. For when the user asks what phase they are in, what workout or food suits them today, or why their energy is up or down, for example "what phase am I in, my last period started September 12th" or "what should I train today?". Needs the first day of their last period. Not for getting pregnant, fertile days, ovulation timing, contraception or pregnancy: this is general wellbeing only, not for pregnancy planning or contraception, and a doctor or pharmacist is the right person for those. When `period_may_be_late` is true the say line says the period may be late and suggests checking with a doctor.

NameTypeReqDescription
countrystring–Two-letter country code (UK is read as GB). Sets the kit links (US, GB and IE get local Amazon links) and the time zone for today. Default from the request.
cycle_lengthinteger–Usual days from one period start to the next, 20 to 45. Default 28.
datestring–Day to ask about, YYYY-MM-DD, a real calendar day. Default today where the user is: from tz, else country, else the request, else UTC.
dietstring–Comma separated: vegetarian, vegan, pescatarian, halal. Food ideas are filtered to suit.
last_periodstringyesFirst day of the user's most recent period, YYYY-MM-DD. Must be within the last 120 days.
last_period_startstring–Older name for last_period, kept for existing callers; last_period is the current name.
period_lengthinteger–Usual days of bleeding, 2 to 10. Default 5.
tzstring–The user's IANA time zone, for example Europe/London or America/Chicago, so today is the user's today. Optional: country is enough in most places.

No output schema declared.

No examples provided.

get_week_ahead ~380

The days ahead by phase. For when the user wants to plan training or meals for the week, for example "plan my training this week around my cycle". Returns each day's likely phase, workout focus, intensity and food focus. Not for getting pregnant, fertile days, ovulation timing, contraception or pregnancy: this is general wellbeing only, not for pregnancy planning or contraception, and it is not a fertility calendar. When `period_may_be_late` is true, `days` is empty and the say line suggests checking with a doctor.

NameTypeReqDescription
countrystring–Two-letter country code (UK is read as GB), used for the time zone of today.
cycle_lengthinteger–Usual cycle length, 20 to 45. Default 28.
datestring–First day of the plan, YYYY-MM-DD, a real calendar day. Default today where the user is: from tz, else country, else the request, else UTC.
daysinteger–How many days, a whole number from 1 to 35. Default 7.
dietstring–Accepted for symmetry with get_todays_phase; the week view has no food list, so it has no effect here.
last_periodstringyesFirst day of the user's most recent period, YYYY-MM-DD. Must be within the last 120 days.
last_period_startstring–Older name for last_period, kept for existing callers; last_period is the current name.
period_lengthinteger–Usual days of bleeding, 2 to 10. Default 5.
tzstring–The user's IANA time zone, for example Europe/London or America/Chicago, so today is the user's today. Optional: country is enough in most places.

No output schema declared.

No examples provided.

list_phases ~68

What each phase usually feels like, with workout and food ideas. For general questions about cycle syncing that need no dates, for example "what should I eat in my luteal phase?". Not for conception, fertile days, contraception or pregnancy: general wellbeing only, not for pregnancy planning or contraception.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Sync My Cycle MCP server?

Sync My Cycle is a hosted endpoint at https://goodturn-mcp.pages.dev/syncmycycle/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · goodturn-mcp.pages.dev

# add to Claude Code
claude mcp add --transport http goodturnstudio-syncmycycle 'https://goodturn-mcp.pages.dev/syncmycycle/mcp'
Common questions

What is the Sync My Cycle MCP server?

Sync My Cycle is an MCP server listed in the public MCP registry as io.github.GoodTurnStudio/syncmycycle. Your likely menstrual cycle phase today and this week, with food and workout ideas. This page covers its hosted endpoint (https://goodturn-mcp.pages.dev/syncmycycle/mcp).

Is the Sync My Cycle MCP server safe to use?

Sync My Cycle scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Sync My Cycle MCP server expose?

Sync My Cycle exposes 3 tools: get_todays_phase, get_week_ahead, list_phases. Their descriptions and schemas cost roughly 856 tokens of context every time the server is loaded.

Does the Sync My Cycle MCP server require authentication?

No. We connected to Sync My Cycle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sync My Cycle MCP server still maintained?

Sync My Cycle is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Sync My Cycle MCP server?

VerifyMCP ran 13 checks on Sync My Cycle, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.