Remote MCP · Endpoint

Business Days and Holidays MCP server

No. Business Days and Holidays answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
271 ms
Tools exposed
6 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Count working days between two dates, add business days to a date, or list public holidays.
Listing
From the official MCP registry (active).
Recent checks of Business Days and Holidays
CheckedResultHandshake
1 hour agoHandshake completed271 ms
1 day agoHandshake completed44 ms
3 days agoHandshake completed37 ms

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

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