# FlightPayback (remote · myflightpayback.com)

Free check: does an airline owe you cash for a delayed or cancelled flight in Canada?

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `myflightpayback.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-myflightpayback-flightpayback/myflightpayback.md), [page](https://verifymcp.io/servers/com-myflightpayback-flightpayback/myflightpayback)

## Channel facts

- Endpoint: `https://myflightpayback.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-myflightpayback-flightpayback 'https://myflightpayback.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-myflightpayback-flightpayback": {
      "url": "https://myflightpayback.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-myflightpayback-flightpayback": {
      "type": "http",
      "url": "https://myflightpayback.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-myflightpayback-flightpayback]
url = "https://myflightpayback.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-myflightpayback-flightpayback": {
      "type": "remote",
      "url": "https://myflightpayback.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-myflightpayback-flightpayback --url 'https://myflightpayback.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-myflightpayback-flightpayback:
    url: "https://myflightpayback.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-myflightpayback-flightpayback": {
      "Transport": "http",
      "Url": "https://myflightpayback.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-myflightpayback-flightpayback -t streamable-http -u 'https://myflightpayback.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-myflightpayback-flightpayback": {
      "type": "http",
      "url": "https://myflightpayback.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 72, +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.

### 2026-11-01 (score 71, +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.

### 2026-10-30 (score 70, +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.

### 2026-10-28 (score 69, +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.

### 2026-10-27 (score 68, 0)

- [cosmetic] “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

### 2026-10-26 (score 68, +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.

### 2026-10-24 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 66)

First indexed and scored.

## MCP tools (3)

### `find_airport` (~63 tokens)

Find an airport

Search airports by city, name or IATA code. Returns up to 8 matches with their IATA codes; Canadian airports are listed first.

Input parameters:

- `query` (string, required): City, airport name or code, e.g. "toronto" or "YUL".

### `find_airline` (~69 tokens)

Find an airline

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.

Input parameters:

- `query` (string, required): A flight number or an airline name.

### `check_flight_compensation` (~782 tokens)

Check flight compensation

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.

Input parameters:

- `acceptedVoucherInWriting` (boolean, required): 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, required): 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, required): Did the airline say the problem was caused by an earlier flight?
- `charter` (string, required): 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, required): IATA code of the FINAL destination on the original ticket (not a connection).
- `disruption` (string, required): Was the flight delayed or cancelled?
- `flightDate` (string, required): Original scheduled departure date, YYYY-MM-DD.
- `marketingCarrierIata` (string, required): 2-character code of the airline on the ticket: the letters of the flight number, e.g. AC for AC 857.
- `notice` (string, required): 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, required): IATA code of the departure airport, e.g. YYZ. Use find_airport if unsure.
- `outcome` (string, required): "travelled" = reached the destination (original or new flight); "refunded" = took a refund instead; "other" = e.g. made their own way.
- `reason` (string, required): 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.

Output parameters:

- `amountCadMax` (number|null)
- `amountCadMin` (number|null)
- `deadlineSoon` (boolean)
- `euOrUkRulesMayAlsoApply` (boolean)
- `lastDayToFile` (string|null)
- `moreInfo` (string)
- `verdict` (string)
- `whereToClaim`
- `whyNotOwed` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-myflightpayback-flightpayback/myflightpayback#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 66

## Common questions

### 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.

### What did VerifyMCP test on the FlightPayback MCP server?

VerifyMCP ran 12 checks on FlightPayback, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FlightPayback: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://myflightpayback.com/mcp
- Website: https://myflightpayback.com/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-myflightpayback-flightpayback/myflightpayback.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-myflightpayback-flightpayback/myflightpayback/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-myflightpayback-flightpayback/myflightpayback.json
- HTML version of this page: https://verifymcp.io/servers/com-myflightpayback-flightpayback/myflightpayback