Remote MCP · Endpoint

Shiftyasan Shift Scheduling MCP server

No. Shiftyasan Shift Scheduling answered an MCP handshake 2 hours ago.

Up · key neededLast checked 2 hours ago

Server URL

https://api.shiftyasan.com/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
com.shiftyasan/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
351 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Generate optimized work shift schedules from staffing demand, availability and fairness rules.
Website
https://api.shiftyasan.com/
Repository
https://github.com/shiftyasan/mcp-server
Listing
From the official MCP registry (active).
Recent checks of Shiftyasan Shift Scheduling
CheckedResultHandshake
2 hours agoHandshake completed351 ms
1 day agoHandshake completed270 ms
2 days agoHandshake completed385 ms
3 days agoHandshake completed395 ms
4 days agoHandshake completed362 ms
5 days agoHandshake completed345 ms
7 days agoHandshake completed348 ms
9 days agoHandshake completed452 ms
12 days agoHandshake completed345 ms
14 days agoHandshake completed701 ms
16 days agoHandshake completed318 ms
18 days agoHandshake completed319 ms
20 days agoHandshake completed299 ms
22 days agoHandshake completed310 ms
24 days agoHandshake completed283 ms
26 days agoHandshake completed324 ms
27 days agoHandshake completed336 ms
29 days agoHandshake completed638 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Shiftyasan Shift Scheduling and makes no claim about it beyond what these checks measured.