Remote MCP · Endpoint

SOS Flights MCP server

No. SOS Flights answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.sosflights.help/mcp

The last check completed an MCP handshake.

Registry name
io.github.codeblockssk/sosflights
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
856 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live reroutes, desk scripts, airport help and EU261/UK261/US DOT rights for disrupted flights.
Listing
From the official MCP registry (active).
Recent checks of SOS Flights
CheckedResultHandshake
1 hour agoHandshake completed856 ms
9 days agoHandshake completed770 ms
10 days agoHandshake completed756 ms
11 days agoHandshake completed843 ms
12 days agoHandshake completed666 ms
14 days agoHandshake completed367 ms
14 days agoHandshake completed709 ms
15 days agoHandshake completed694 ms
17 days agoHandshake completed647 ms
19 days agoHandshake completed910 ms
21 days agoHandshake completed850 ms
24 days agoHandshake completed683 ms
26 days agoHandshake completed677 ms

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

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