Remote MCP · Endpoint

When Works For You MCP server

No. When Works For You answered an MCP handshake 58 minutes ago.

UpLast checked 58 minutes ago

Server URL

https://whenworksforyou.com/mcp

The last check completed an MCP handshake.

Registry name
com.whenworksforyou/wwfy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
292 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find a date that works for a group: answer a poll from its link, or create one and invite guests.
Listing
From the official MCP registry (active).
Recent checks of When Works For You
CheckedResultHandshake
58 minutes agoHandshake completed292 ms
1 day agoHandshake completed381 ms
4 days agoHandshake completed294 ms
6 days agoHandshake completed131 ms
9 days agoHandshake completed145 ms
11 days agoHandshake completed292 ms
13 days agoHandshake completed267 ms
15 days agoHandshake completed280 ms
17 days agoHandshake completed173 ms
19 days agoHandshake completed286 ms
21 days agoHandshake completed135 ms
22 days agoHandshake completed399 ms
23 days agoHandshake completed163 ms

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

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 When Works For You and makes no claim about it beyond what these checks measured.