Remote MCP · Endpoint

Rotase MCP server

No. Rotase answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rotase.com/mcp

The last check completed an MCP handshake.

Registry name
com.rotase/rotase
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
546 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.
Website
https://rotase.com/
Listing
From the official MCP registry (active).
Recent checks of Rotase
CheckedResultHandshake
1 hour agoHandshake completed546 ms
9 days agoHandshake completed475 ms
9 days agoHandshake completed561 ms
11 days agoHandshake completed548 ms
12 days agoHandshake completed482 ms
13 days agoHandshake completed448 ms
14 days agoHandshake completed479 ms
14 days agoHandshake completed460 ms
16 days agoHandshake completed469 ms
19 days agoHandshake completed455 ms
21 days agoHandshake completed484 ms
24 days agoHandshake completed471 ms
26 days agoHandshake completed474 ms
28 days agoHandshake completed471 ms

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

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