Remote MCP · Endpoint

Workday Calendar MCP server

No. Workday Calendar answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://workday-calendar.regnotes.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.regnotes.workday-calendar/workday-calendar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
270 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Public holidays and business-day math (T+N, counts) for many countries; pay per call via x402
Listing
From the official MCP registry (active).
Recent checks of Workday Calendar
CheckedResultHandshake
34 minutes agoHandshake completed270 ms
3 days agoHandshake completed457 ms
13 days agoHandshake completed639 ms
13 days agoHandshake completed525 ms
15 days agoHandshake completed479 ms
16 days agoHandshake completed304 ms
17 days agoHandshake completed324 ms
18 days agoHandshake completed301 ms
18 days agoHandshake completed407 ms
20 days agoHandshake completed350 ms
22 days agoHandshake completed824 ms
25 days agoHandshake completed53 ms

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

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