Remote MCP · Endpoint

Shift Scheduler MCP server

No. Shift Scheduler answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://staff-scheduling.kindoflost.com/mcp

The last check completed an MCP handshake.

Registry name
com.kindoflost.staff-scheduling/shift-scheduler
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Builds optimal 24/7 staff rosters with a real MILP solver: rest rules, skills, nights, fairness.
Listing
From the official MCP registry (active).
Recent checks of Shift Scheduler
CheckedResultHandshake
1 hour agoHandshake completed89 ms
2 days agoHandshake completed75 ms
4 days agoHandshake completed109 ms
6 days agoHandshake completed98 ms
8 days agoHandshake completed329 ms
9 days agoHandshake completed82 ms
11 days agoHandshake completed200 ms
12 days agoHandshake completed82 ms
13 days agoHandshake completed59 ms
16 days agoHandshake completed66 ms
17 days agoHandshake completed82 ms
19 days agoHandshake completed101 ms
21 days agoHandshake completed83 ms
22 days agoHandshake completed78 ms
23 days agoHandshake completed78 ms

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

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 Shift Scheduler and makes no claim about it beyond what these checks measured.