Remote MCP · Endpoint

Business Days MCP server

No. Business Days answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://tools.profitpather.com/days/mcp

The last check completed an MCP handshake.

Registry name
com.profitpather.tools/business-days
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public holidays and working-day maths for 200+ countries, cross-checked across three providers.
Listing
From the official MCP registry (active).
Recent checks of Business Days
CheckedResultHandshake
20 minutes agoHandshake completed157 ms
9 days agoHandshake completed76 ms
9 days agoHandshake completed48 ms
11 days agoHandshake completed44 ms
12 days agoHandshake completed263 ms
13 days agoHandshake completed82 ms
14 days agoHandshake completed173 ms
15 days agoHandshake completed51 ms
16 days agoHandshake completed51 ms
19 days agoHandshake completed147 ms
21 days agoHandshake completed70 ms
24 days agoHandshake completed106 ms
26 days agoHandshake completed104 ms
28 days agoHandshake completed53 ms

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

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