Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
FlightPayback is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Free check: does an airline owe you cash for a delayed or cancelled flight in Canada?
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http flightpayback-mcp https://myflightpayback.com/mcp
# 2 — ask your agent for something these tools do
# find_airport, find_airline, check_flight_compensation
FlightPayback costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http flightpayback-mcp https://myflightpayback.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search airports by city, name or IATA code. Returns up to 8 matches with their IATA codes; Canadian airports are listed first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | City, airport name or code, e.g. "toronto" or "YUL". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A flight number or an airline name. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| disruption | string | yes | Was the flight delayed or cancelled? |
| originIata | string | yes | IATA code of the departure airport, e.g. YYZ. Use find_airport if unsure. |
| destinationIata | string | yes | IATA code of the FINAL destination on the original ticket (not a connection). |
| connectionIatas | array | no | IATA codes of connecting airports, in order. Empty for a direct flight. |
| marketingCarrierIata | string | yes | 2-character code of the airline on the ticket: the letters of the flight number, e.g. AC for AC 857. |
| operatingCarrierIata | string | no | Only if a different airline actually flew the plane ("operated by ..."): its 2-character code. |
| charter | string | yes | Was it a charter or package-holiday flight? Use "unsure" if the passenger does not know. |
| flightDate | string | yes | Original scheduled departure date, YYYY-MM-DD. |
| scheduledArrival | string | no | Scheduled arrival at the final destination, as on the original ticket, local time there: YYYY-MM-DDTHH:mm. With actualArrival; or use arrivalDelay instead. |
| actualArrival | string | no | When the passenger actually arrived at the final destination (aircraft door opened), local time there: YYYY-MM-DDTHH:mm. |
| arrivalDelay | string | no | 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. |
| outcome | string | yes | "travelled" = reached the destination (original or new flight); "refunded" = took a refund instead; "other" = e.g. made their own way. |
| delayAtRefundAtLeast3h | boolean | no | Only for a delayed flight where the passenger took a refund: was it at least 3 hours late at that point? |
| notice | string | yes | When did the airline tell the passenger? "within_14_days" includes being told at the airport. |
| 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 (Schedu |
| blamedEarlierFlight | boolean | yes | Did the airline say the problem was caused by an earlier flight? |
| acceptedVoucherInWriting | boolean | yes | Did the passenger accept a voucher or credit instead of cash, in writing? |
| alreadyCompensated | boolean | yes | Has the passenger already been paid compensation for this disruption (by the airline or under another country's rules)? |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FlightPayback or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| find_airport | no tags | |
| find_airline | no tags | |
| check_flight_compensation | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish FlightPayback can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.