Remote MCP · Endpoint

Business Days & Workday Calc MCP server

No. Business Days & Workday Calc answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://businessdays.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/business-days
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Count workdays, office days and PTO days, or list bank holidays and school breaks.
Listing
From the official MCP registry (active).
Recent checks of Business Days & Workday Calc
CheckedResultHandshake
4 hours agoHandshake completed290 ms
2 days agoHandshake completed320 ms
5 days agoHandshake completed325 ms
7 days agoHandshake completed307 ms
9 days agoHandshake completed370 ms
11 days agoHandshake completed329 ms
13 days agoHandshake completed84 ms
15 days agoHandshake completed362 ms
17 days agoHandshake completed272 ms
18 days agoHandshake completed306 ms
20 days agoHandshake completed271 ms
21 days agoHandshake completed44 ms
23 days agoHandshake completed37 ms

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

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