Remote MCP · Endpoint

WorkdayAPI MCP server

No. WorkdayAPI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://workdayapi.mike-tusa.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.mike-tusa.workdayapi/workdayapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Business-day and public-holiday math for 29 countries: add business days, days between, holidays.
Listing
From the official MCP registry (active).
Recent checks of WorkdayAPI
CheckedResultHandshake
1 hour agoHandshake completed73 ms
12 hours agoHandshake completed345 ms
1 day agoHandshake completed82 ms
2 days agoHandshake completed60 ms
4 days agoHandshake completed88 ms
4 days agoHandshake completed67 ms
5 days agoHandshake completed83 ms
7 days agoHandshake completed76 ms
8 days agoHandshake completed76 ms
11 days agoHandshake completed91 ms
13 days agoHandshake completed74 ms
16 days agoHandshake completed83 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed69 ms
22 days agoHandshake completed91 ms
24 days agoHandshake completed92 ms

The last 16 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.

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