Remote MCP · Endpoint

BridgeDays MCP server

No. BridgeDays answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bridgedays.eu/mcp

The last check completed an MCP handshake.

Registry name
io.github.maleksandrov/bridgedays
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
224 ms
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Plan annual leave around public holidays: bridge days and long weekends for 200+ countries.
Listing
From the official MCP registry (active).
Recent checks of BridgeDays
CheckedResultHandshake
1 hour agoHandshake completed224 ms
3 days agoHandshake completed222 ms
12 days agoHandshake completed268 ms
13 days agoHandshake completed382 ms
15 days agoHandshake completed220 ms
15 days agoFailed - the request timed out—
17 days agoHandshake completed187 ms
18 days agoHandshake completed221 ms
18 days agoHandshake completed207 ms
20 days agoHandshake completed217 ms
22 days agoHandshake completed387 ms
25 days agoHandshake completed234 ms
27 days agoHandshake completed258 ms
29 days agoHandshake completed229 ms

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

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