Remote MCP · Endpoint

weekendflights MCP server

No. weekendflights answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://weekendflights.app/mcp

The last check completed an MCP handshake.

Registry name
app.weekendflights/weekendflights
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
340 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Weekend flight price calendar: the cheapest round trip for every weekend of the next 12 months.
Listing
From the official MCP registry (active).
Recent checks of weekendflights
CheckedResultHandshake
1 hour agoHandshake completed340 ms
1 day agoHandshake completed937 ms
4 days agoHandshake completed774 ms
6 days agoHandshake completed910 ms
9 days agoHandshake completed895 ms
11 days agoHandshake completed277 ms
13 days agoHandshake completed859 ms
15 days agoHandshake completed525 ms
17 days agoHandshake completed419 ms
19 days agoHandshake completed745 ms
21 days agoHandshake completed333 ms
22 days agoHandshake completed997 ms
24 days agoHandshake completed817 ms
25 days agoHandshake completed641 ms
27 days agoHandshake completed754 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 weekendflights and makes no claim about it beyond what these checks measured.