FlightPayback
REMOTE · MYFLIGHTPAYBACK.COM
Free check: does an airline owe you cash for a delayed or cancelled flight in Canada?
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1023 tokens (~341/item across 3 items; 3 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 Management43
- Stability observed for 13 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 (33% 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 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.
- 1 Nov 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.
- 30 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.
- 28 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.
- 27 Oct 26 0
- “check_flight_compensation” added an optional parameter “arrivalDelay” cosmetic
- “check_flight_compensation” reworded the description of “actualArrival” cosmetic
- “check_flight_compensation” reworded the description of “scheduledArrival” cosmetic
- “check_flight_compensation” made “scheduledArrival” optional cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 66
First indexed and scored.
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 5 Nov 2026 · Probed https://myflightpayback.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=myflightpayback.com | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b7da19fffe91c0d13b32e8c147a668d |
| SANs: myflightpayback.com, *.myflightpayback.com | ||||||
| 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 myflightpayback.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| myflightpayback.com. | 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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self' https://cloudflareinsights.com; font-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://myflightpayback.com/mcp | Verified | 200 | |
| http (plaintext) | http://myflightpayback.com/mcp | Inconclusive | 405 |
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 →
check_flight_compensation Check flight compensation ~782
Check whether an airline owes cash compensation for a delayed or cancelled flight under Canada's Air Passenger Protection Regulations, and how much. Ask the passenger for every answer; don't guess. Returns the verdict, amount per passenger and the last day to file. General information, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedVoucherInWriting | boolean | yes | Did the passenger accept a voucher or credit instead of cash, in writing? |
| actualArrival | string | – | When the passenger actually arrived at the final destination (aircraft door opened), local time there: YYYY-MM-DDTHH:mm. |
| alreadyCompensated | boolean | yes | Has the passenger already been paid compensation for this disruption (by the airline or under another country's rules)? |
| arrivalDelay | string | – | If the passenger doesn't know the exact times: how late they reached the final destination. When outcome is "travelled", give scheduledArrival + actualArrival, or this. |
| blamedEarlierFlight | boolean | yes | Did the airline say the problem was caused by an earlier flight? |
| charter | string | yes | Was it a charter or package-holiday flight? Use "unsure" if the passenger does not know. |
| connectionIatas | array | – | IATA codes of connecting airports, in order. Empty for a direct flight. |
| delayAtRefundAtLeast3h | boolean | – | Only for a delayed flight where the passenger took a refund: was it at least 3 hours late at that point? |
| destinationIata | string | yes | IATA code of the FINAL destination on the original ticket (not a connection). |
| disruption | string | yes | Was the flight delayed or cancelled? |
| flightDate | string | yes | Original scheduled departure date, YYYY-MM-DD. |
| marketingCarrierIata | string | yes | 2-character code of the airline on the ticket: the letters of the flight number, e.g. AC for AC 857. |
| notice | string | yes | When did the airline tell the passenger? "within_14_days" includes being told at the airport. |
| operatingCarrierIata | string | – | Only if a different airline actually flew the plane ("operated by ..."): its 2-character code. |
| originIata | string | yes | IATA code of the departure airport, e.g. YYZ. Use find_airport if unsure. |
| outcome | string | yes | "travelled" = reached the destination (original or new flight); "refunded" = took a refund instead; "other" = e.g. made their own way. |
| reason | string | yes | The reason the airline gave, mapped to the closest value. Airline operations: crew_shortage (Crew or staff shortage), scheduled_maintenance (Scheduled maintenance), schedule_or_aircraft_change (Sched… |
| scheduledArrival | string | – | Scheduled arrival at the final destination, as on the original ticket, local time there: YYYY-MM-DDTHH:mm. With actualArrival; or use arrivalDelay instead. |
| Name | Type | Req | Description |
|---|---|---|---|
| amountCadMax | number|null | yes | – |
| amountCadMin | number|null | yes | – |
| deadlineSoon | boolean | yes | – |
| euOrUkRulesMayAlsoApply | boolean | yes | – |
| lastDayToFile | string|null | yes | – |
| moreInfo | string | yes | – |
| verdict | string | yes | – |
| whereToClaim | – | yes | – |
| whyNotOwed | array | yes | – |
No examples provided.
find_airline Find an airline ~69
Find an airline’s 2-character code from a flight number (e.g. "AC 857") or a name (e.g. "WestJet"). An airline missing from the list can still be checked by its code.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A flight number or an airline name. |
No output schema declared.
No examples provided.
find_airport Find an airport ~63
Search airports by city, name or IATA code. Returns up to 8 matches with their IATA codes; Canadian airports are listed first.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | City, airport name or code, e.g. "toronto" or "YUL". |
No output schema declared.
No examples provided.
How do I install the FlightPayback MCP server?
FlightPayback is a hosted endpoint at https://myflightpayback.com/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 · myflightpayback.com
claude mcp add --transport http com-myflightpayback-flightpayback 'https://myflightpayback.com/mcp'
What is the FlightPayback MCP server?
FlightPayback is an MCP server listed in the public MCP registry as com.myflightpayback/flightpayback. Free check: does an airline owe you cash for a delayed or cancelled flight in Canada? This page covers its hosted endpoint (https://myflightpayback.com/mcp).
Is the FlightPayback MCP server safe to use?
FlightPayback scores 72 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 FlightPayback MCP server expose?
FlightPayback exposes 3 tools: find_airport, find_airline, check_flight_compensation. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.
Does the FlightPayback MCP server require authentication?
No. We connected to FlightPayback without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FlightPayback MCP server still maintained?
FlightPayback is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.