Remote MCP · Endpoint

Holiday Calendar MCP server

No. Holiday Calendar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://starter.modernmustardseed.com/holidays

The last check completed an MCP handshake.

Registry name
com.modernmustardseed/holiday-calendar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
133 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
U.S. federal holidays with observed dates and business-day math. Example from an open-source kit.
Listing
From the official MCP registry (active).
Recent checks of Holiday Calendar
CheckedResultHandshake
1 hour agoHandshake completed133 ms
1 day agoHandshake completed91 ms
2 days agoHandshake completed64 ms
3 days agoHandshake completed87 ms
4 days agoHandshake completed68 ms
5 days agoHandshake completed81 ms
6 days agoHandshake completed76 ms
9 days agoHandshake completed82 ms
11 days agoHandshake completed85 ms
14 days agoHandshake completed335 ms
16 days agoHandshake completed67 ms
18 days agoHandshake completed64 ms
20 days agoHandshake completed119 ms
22 days agoHandshake completed67 ms
24 days agoHandshake completed115 ms

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