Remote MCP · Endpoint

Spin My Day MCP server

No. Spin My Day answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/spinmyday
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plans a whole day out in any city, matched to the weather, your mood and diet.
Listing
From the official MCP registry (active).
Recent checks of Spin My Day
CheckedResultHandshake
43 minutes agoHandshake completed98 ms
9 days agoHandshake completed28 ms
10 days agoHandshake completed50 ms
11 days agoHandshake completed26 ms
12 days agoHandshake completed31 ms
14 days agoHandshake completed37 ms
15 days agoHandshake completed17 ms
15 days agoHandshake completed73 ms
17 days agoHandshake completed29 ms
19 days agoHandshake completed20 ms
22 days agoHandshake completed16 ms
24 days agoHandshake completed39 ms
26 days agoHandshake completed23 ms
29 days agoHandshake completed46 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 Spin My Day and makes no claim about it beyond what these checks measured.