Remote MCP · Endpoint

Spin My Day MCP server

No. Spin My Day answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
39 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
2 hours agoHandshake completed39 ms
2 days agoHandshake completed23 ms
4 days agoHandshake completed46 ms
6 days agoHandshake completed69 ms
8 days agoHandshake completed67 ms
10 days agoHandshake completed24 ms
12 days agoHandshake completed12 ms
13 days agoHandshake completed18 ms
14 days agoHandshake completed13 ms
16 days agoHandshake completed21 ms
18 days agoHandshake completed19 ms
20 days agoHandshake completed22 ms
22 days agoHandshake completed20 ms
23 days agoHandshake completed26 ms

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

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.