Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SOS Flights

REMOTE · WWW.SOSFLIGHTS.HELP

Live reroutes, desk scripts, airport help and EU261/UK261/US DOT rights for disrupted flights.

+4 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1773 tokens (~197/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://www.sosflights.help/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.sosflights.help CN=WE1,O=Google Trust Services,C=US 9 Sept 2026 8 Dec 2026 ECDSA 256 ECDSA-SHA256 a93045396eeac1a813a239b303a49449
SANs: www.sosflights.help
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.sosflights.help. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
help. present 10505, 58472 13, 13 Verified
sosflights.help. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.sosflights.help/mcp Verified 200
http (plaintext) http://www.sosflights.help/mcp HTTPS enforced 301 https://www.sosflights.help/mcp
MCP tools · 9 exposed · ~1,686 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
sos_airport_help ~97

Lists hotel, lounge and transfer search links for an airport, nearby alternative airports with directions, and who pays for a hotel under EU and UK rules. Links only, nothing is booked. Covers about 100 airports in Europe, North America and Asia.

NameTypeReqDescription
airportstringyesIATA code of the airport where the traveller is, for example VIE.
needstring–What the traveller needs. Defaults to all.
NameTypeReqDescription
airportobjectyes–
linksarrayyes–
nearby_airportsarrayyes–
who_paysarrayyes–

No examples provided.

sos_check_rights ~339

Checks a cancelled, delayed, overbooked or missed-connection flight against EU261, UK261 and US DOT rules. Returns the law that applies, up to three options (refund, re-routing), the care the airline owes (meals, hotel), a compensation range per passenger with its conditions, warnings and facts that would sharpen the answer. Advice only, not legal advice.

NameTypeReqDescription
arrival_delay_minutesinteger–Expected arrival delay at the final destination, in minutes.
carrierstring–IATA code of the operating airline, for example FR, W6 or OS.
causestring–Reason given by the airline, if known.
departure_delay_minutesinteger–Departure delay in minutes, if different from the arrival delay.
destinationstringyesIATA code of the final destination on the booking, for example LHR.
notice_daysinteger–Cancellations: days between the notice and scheduled departure.
originstringyesIATA code of the departure airport, for example VIE.
overnightboolean–True if the traveller must stay overnight.
reroute_arrives_later_minutesinteger–Re-routing offered: how many minutes later it arrives than the original flight.
reroute_departs_earlier_minutesinteger–Re-routing offered: how many minutes earlier it departs than the original flight.
single_bookingboolean–Missed connections: were all flights on one booking?
typestringyesWhat happened to the flight.
volunteeredboolean–Denied boarding: did the traveller volunteer?
NameTypeReqDescription
carearrayyes–
compensationobject––
distance_kmnumber––
follow_upsarrayyes–
help_urlstringyes–
last_verifiedstringyes–
lawstringyes–
law_reasonstringyes–
optionsarrayyes–
sourcesarrayyes–
warningsarrayyes–

No examples provided.

sos_desk_script ~331

Writes 1 to 3 short, polite sentences for a traveller to say to the airline agent, asking for re-routing, care or a refund. The sentences are in the traveller's language and cite the regulation that applies.

NameTypeReqDescription
arrival_delay_minutesinteger–Expected arrival delay at the final destination, in minutes.
carrierstring–IATA code of the operating airline, for example FR, W6 or OS.
causestring–Reason given by the airline, if known.
departure_delay_minutesinteger–Departure delay in minutes, if different from the arrival delay.
destinationstringyesIATA code of the final destination on the booking, for example LHR.
langstring–Traveller's language for any text meant to be read out or copied. Defaults to en.
notice_daysinteger–Cancellations: days between the notice and scheduled departure.
originstringyesIATA code of the departure airport, for example VIE.
overnightboolean–True if the traveller must stay overnight.
reroute_arrives_later_minutesinteger–Re-routing offered: how many minutes later it arrives than the original flight.
reroute_departs_earlier_minutesinteger–Re-routing offered: how many minutes earlier it departs than the original flight.
single_bookingboolean–Missed connections: were all flights on one booking?
typestringyesWhat happened to the flight.
volunteeredboolean–Denied boarding: did the traveller volunteer?
NameTypeReqDescription
langstringyes–
lawstringyes–
sayarrayyes–

No examples provided.

sos_find_alternatives ~220

Searches live one-way flights from the traveller's airport and airports within 300 km to their destination on one date, ordered by earliest arrival, with price in EUR, stops, ground distance to the alternative airport and rail operator links for trips under 1,200 km. Returns 10 options per page; times are local to each airport. Nothing is booked.

NameTypeReqDescription
cursorstring–next_cursor from the previous page.
datestringyesTravel date, ISO 8601, for example 2026-10-02. From today up to 365 days ahead.
destinationstringyesIATA airport or city code of the destination, for example LON.
include_nearby_airportsboolean–Also search from the two nearest airports within 300 km. Defaults to true.
limitinteger–Options per page, 1 to 25. Defaults to 10.
originstringyesIATA code of the airport where the traveller is now, for example BTS.
NameTypeReqDescription
flightsarrayyes–
next_cursorstring––
railarrayyes–
who_paysarrayyes–

No examples provided.

sos_get_case ~96

Returns the status of an SOS Flights case by its case code: whether it is active, the team's recommended solution once there is one, the last 10 chat messages for chat cases, and the case page link.

NameTypeReqDescription
case_codestringyes8-character case code from the payment confirmation or case page, for example 53039309.
langstring–Language of the case page link. Defaults to en.
NameTypeReqDescription
activebooleanyes–
case_codestringyes–
case_urlstringyes–
channelstringyes–
messagesarrayyes–
recommended_solutionstring––
statusstringyes–

No examples provided.

sos_open_case ~144

Opens the case prepared with a confirmation_token, after the traveller confirmed it. Returns the case code, which is the key to the case afterwards, the case page and either a payment link (the case becomes active after payment) or, with an access code, an active case.

NameTypeReqDescription
confirmation_tokenstringyesconfirmation_token from the prepare step, for example sc_3qJ8vT0kPzL1mW6xR2aYbQ. Valid for 15 minutes.
idempotency_keystring–Key that makes a retry safe: a repeated key returns the first result. Defaults to one key per confirmation_token.
NameTypeReqDescription
activebooleanyes–
case_codestringyes–
case_urlstringyes–
channelstringyes–
checkout_urlstring––
statusstringyes–

No examples provided.

sos_prepare_case ~248

Checks the details for a case handled by the SOS Flights team (rebooking help, hotel, evidence and follow-up) and returns what will be submitted, the price (a one-time fee, or covered by a valid access code) and a confirmation_token valid for 15 minutes. Nothing is created or charged. No account is needed.

NameTypeReqDescription
access_codestring–Prepaid access code, for example from OneYear Protection.
channelstringyesHow the team talks to the traveller, as the traveller chose: whatsapp, or chat in this assistant conversation and on the case page.
emailstringyesTraveller's email for the payment receipt and case updates.
langstring–Language for the payment and case pages. Defaults to en.
phonestringyesTraveller's mobile number with country code, for example +421905123456. The WhatsApp number, or an urgent contact for chat.
situation_summarystringyesSummary for the team: airport, number of travellers and children's ages, what happened, flight number and booking reference, destination and urgency, constraints, any safety risk.
surnamestring–Traveller's surname.
NameTypeReqDescription
channelstringyes–
confirmation_tokenstringyes–
emailstringyes–
expires_atstringyes–
paymentstringyes–
phonestringyes–
price_eurnumberyes–
situation_summarystringyes–
surnamestring––

No examples provided.

sos_prepare_message ~89

Checks a message from the traveller to the SOS Flights team on an active chat case and returns it with a confirmation_token valid for 15 minutes. Nothing is sent. WhatsApp cases continue in WhatsApp.

NameTypeReqDescription
case_codestringyes8-character case code from the payment confirmation or case page.
messagestringyesThe traveller's message to the team, in their own words.
NameTypeReqDescription
case_codestringyes–
confirmation_tokenstringyes–
expires_atstringyes–
messagestringyes–

No examples provided.

sos_send_message ~122

Sends the message prepared with a confirmation_token to the SOS Flights team, after the traveller confirmed it. The team's reply appears in the case status and on the case page.

NameTypeReqDescription
confirmation_tokenstringyesconfirmation_token from the prepare step, for example sc_3qJ8vT0kPzL1mW6xR2aYbQ. Valid for 15 minutes.
idempotency_keystring–Key that makes a retry safe: a repeated key returns the first result. Defaults to one key per confirmation_token.
NameTypeReqDescription
case_codestringyes–
sentbooleanyes–

No examples provided.

Install

How do I install the SOS Flights MCP server?

SOS Flights is a hosted endpoint at https://www.sosflights.help/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.sosflights.help

# add to Claude Code
claude mcp add --transport http codeblockssk-sosflights 'https://www.sosflights.help/mcp'
Common questions

What is the SOS Flights MCP server?

SOS Flights is an MCP server listed in the public MCP registry as io.github.codeblockssk/sosflights. Live reroutes, desk scripts, airport help and EU261/UK261/US DOT rights for disrupted flights. This page covers its hosted endpoint (https://www.sosflights.help/mcp).

Is the SOS Flights MCP server safe to use?

SOS Flights scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SOS Flights MCP server expose?

SOS Flights exposes 9 tools: sos_check_rights, sos_desk_script, sos_airport_help, sos_find_alternatives, sos_prepare_case, and 4 more. Their descriptions and schemas cost roughly 1,686 tokens of context every time the server is loaded.

Does the SOS Flights MCP server require authentication?

No. We connected to SOS Flights without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SOS Flights MCP server still maintained?

SOS Flights is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.