# FlightFix (remote · flight-fix.magicteams.ai)

EU261/UK261 flight compensation check, rights and claim letters. Free.

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

## Components

- remote · `flight-fix.magicteams.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/everyai-com-flight-fix/flight-fix.md), [page](https://verifymcp.io/servers/everyai-com-flight-fix/flight-fix)

## Channel facts

- Endpoint: `https://flight-fix.magicteams.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1306 tokens (~261/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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 (100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 FlightFix MCP server?

FlightFix is a hosted endpoint at https://flight-fix.magicteams.ai/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 everyai-com-flight-fix 'https://flight-fix.magicteams.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "everyai-com-flight-fix": {
      "url": "https://flight-fix.magicteams.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "everyai-com-flight-fix": {
      "type": "http",
      "url": "https://flight-fix.magicteams.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.everyai-com-flight-fix]
url = "https://flight-fix.magicteams.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "everyai-com-flight-fix": {
      "type": "remote",
      "url": "https://flight-fix.magicteams.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add everyai-com-flight-fix --url 'https://flight-fix.magicteams.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  everyai-com-flight-fix:
    url: "https://flight-fix.magicteams.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "everyai-com-flight-fix": {
      "Transport": "http",
      "Url": "https://flight-fix.magicteams.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add everyai-com-flight-fix -t streamable-http -u 'https://flight-fix.magicteams.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "everyai-com-flight-fix": {
      "type": "http",
      "url": "https://flight-fix.magicteams.ai/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-10-22 (score 78, +1)

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

### 2026-10-20 (score 77, +1)

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

### 2026-10-18 (score 76, +1)

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

### 2026-10-16 (score 75, +1)

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

### 2026-10-13 (score 74, +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-12 (score 73, +1)

- [security] Tool “disruption_rights” rewrote its description, which is the text the model reads
- [cosmetic] “disruption_rights” added an optional parameter “carrier_country”
- [cosmetic] “disruption_rights” reworded the description of “notice_days”
- [cosmetic] “generate_claim_letter” reworded the description of “claimed_amount”
- [cosmetic] “generate_claim_letter” reworded the description of “scheme”

### 2026-10-10 (score 72, −1)

- [security] Tool “check_compensation” rewrote its description, which is the text the model reads
- [security] Tool “claim_timeline” rewrote its description, which is the text the model reads
- [security] Tool “compensation_table” rewrote its description, which is the text the model reads
- [security] Tool “disruption_rights” rewrote its description, which is the text the model reads
- [security] Tool “generate_claim_letter” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 142 → 241
- [functional] Schema quality: good → excellent
- [cosmetic] “check_compensation” reworded the description of “arrival”
- [cosmetic] “check_compensation” reworded the description of “arrival_delay_hours”
- [cosmetic] “check_compensation” reworded the description of “carrier_country”
- [cosmetic] “check_compensation” reworded the description of “departure”
- [cosmetic] “check_compensation” reworded the description of “disrupted”
- [cosmetic] “check_compensation” reworded the description of “distance_km”
- [cosmetic] “check_compensation” reworded the description of “notice_days”
- [cosmetic] “check_compensation” reworded the description of “reason_category”
- [cosmetic] “check_compensation” reworded the description of “reroute_arrival_delay_hours”
- [cosmetic] “check_compensation” reworded the description of “rerouted”
- [cosmetic] “claim_timeline” reworded the description of “flight_date”
- [cosmetic] “claim_timeline” reworded the description of “scheme”
- [cosmetic] “disruption_rights” reworded the description of “arrival”
- [cosmetic] “disruption_rights” reworded the description of “arrival_delay_hours”
- [cosmetic] “disruption_rights” reworded the description of “departure”
- [cosmetic] “disruption_rights” reworded the description of “disrupted”
- [cosmetic] “disruption_rights” reworded the description of “notice_days”
- [cosmetic] “generate_claim_letter” reworded the description of “airline_name”
- [cosmetic] “generate_claim_letter” reworded the description of “arrival”
- [cosmetic] “generate_claim_letter” reworded the description of “booking_reference”
- [cosmetic] “generate_claim_letter” reworded the description of “claimed_amount”
- [cosmetic] “generate_claim_letter” reworded the description of “currency”
- [cosmetic] “generate_claim_letter” reworded the description of “departure”
- [cosmetic] “generate_claim_letter” reworded the description of “flight_date”
- [cosmetic] “generate_claim_letter” reworded the description of “flight_number”
- [cosmetic] “generate_claim_letter” reworded the description of “incident_summary”
- [cosmetic] “generate_claim_letter” reworded the description of “passenger_name”
- [cosmetic] “generate_claim_letter” reworded the description of “scheme”

### 2026-10-09 (score 73, +7)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 29% → 100%
- [functional improvement] Stability: unverified → 0.17
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: fair → good

## MCP tools (5)

### `check_compensation` (~415 tokens)

Check compensation

Assess one disrupted flight under EU261/UK261: works out which scheme applies (or none), route distance and band, whether fixed compensation is due and how much (EUR/GBP), care rights, the stated reason's effect, and next steps. Use for 'what am I owed for my flight?'. Do NOT use to write the claim; use generate_claim_letter.

Input parameters:

- `arrival` (string, required): Final arrival airport 3-letter IATA code, case-insensitive, e.g. JFK
- `arrival_delay_hours` (number): Hours late at the final destination, e.g. 4.5. Drives delay compensation (>= 3h) and care. Default 0.
- `carrier_country` (string): Operating airline's 2-letter country code, e.g. DE for Lufthansa, US for United. Needed for flights arriving into the EU/UK from outside.
- `departure` (string, required): Departure airport 3-letter IATA code, case-insensitive, e.g. LHR
- `disrupted` (string, required): What happened: delayed (arrived late) or cancelled.
- `distance_km` (number): Override the computed great-circle distance in km, e.g. 5540. Both airports must still be known IATA codes.
- `notice_days` (number): For cancellations: days of notice the airline gave before departure, e.g. 3. 14+ days means no fixed compensation. Default 0.
- `reason_category` (string): Cause the airline gave: weather, atc, security, political, strike_atc (third-party strike) are exempt; technical, strike_airline, other are not; crew is case-by-case. Default unknown.
- `reroute_arrival_delay_hours` (number): For re-routed cancellations: hours the replacement arrived after the original schedule, e.g. 2. Default 0.
- `rerouted` (boolean): For cancellations: true if the airline re-routed you on another flight. Default false.

Output parameters:

- `band` (string): Distance band: short <=1500 km, medium <=3500 km, long beyond.
- `care_rights` (object): Duty-of-care entitlements (meals, hotel, calls).
- `compensation` (object): Fixed-compensation outcome.
- `disclaimer` (string): Not-legal-advice disclaimer to show the user.
- `distance_km` (number): Route distance in km used for the band.
- `jurisdiction_reason` (string): Why that scheme does or does not apply.
- `next_steps` (array): Recommended next actions in order.
- `reason` (object): Assessment of the disruption cause.
- `route` (object): Resolved airports and countries.
- `scheme` (string): Passenger-rights scheme that applies to this route.

### `compensation_table` (~70 tokens)

Compensation table

Return the general EU261/UK261 reference: compensation amounts per distance band (EUR and GBP), when care starts, the main eligibility rules and claim time limits. Use when the user asks how the rules work or what the amounts are. Do NOT use to assess a specific flight; use check_compensation.

Output parameters:

- `claim_windows` (string): Time limits for filing claims (EU and UK).
- `disclaimer` (string): Not-legal-advice disclaimer to show the user.
- `eligibility_summary` (array): Key eligibility rules, one per entry.
- `rules` (array): Compensation amounts per distance band.

### `disruption_rights` (~272 tokens)

Disruption rights

List passenger rights for a disruption: first works out whether EU261/UK261 covers the route (as check_compensation does), then gives refund/re-routing, care by band, 5-hour refund, notice-based cancellation compensation rules, denied boarding and escalation. If no scheme applies, gives general guidance only. Does not compute money owed; use check_compensation.

Input parameters:

- `arrival` (string, required): Arrival airport 3-letter IATA code, case-insensitive, e.g. FCO
- `arrival_delay_hours` (number): For delays: hours late, e.g. 5. At 5h+ the refund option is added. Default 0.
- `carrier_country` (string): Operating airline's 2-letter country code, e.g. DE. Needed for flights arriving into the EU/UK from outside.
- `departure` (string, required): Departure airport 3-letter IATA code, case-insensitive, e.g. CDG
- `disrupted` (string, required): What happened: delayed, cancelled, or denied_boarding (bumped/overbooked).
- `notice_days` (number): For cancellations: days of notice given, e.g. 3. 14+ days means no fixed compensation (refund/re-routing and care still apply); under 14 sets the re-routing conditions.

Output parameters:

- `band` (string): Distance band, or 'unknown' if an airport is not recognised.
- `complaint_path` (array): Escalation steps from airline to regulator to court.
- `disclaimer` (string): Not-legal-advice disclaimer to show the user.
- `disrupted` (string): Disruption type that was assessed.
- `distance_km` (number|null): Route distance in km, or null if an airport is unknown.
- `entitled_rights` (array): Rights that apply under the scheme, or general guidance when no scheme applies, one per entry.
- `jurisdiction_reason` (string): Why that scheme does or does not apply.
- `scheme` (string): Scheme covering the route; none = EU261/UK261 do not apply (general guidance only); unknown = airport not recognised.

### `claim_timeline` (~136 tokens)

Claim timeline

Give claim-deadline guidance for a flight under EU261 or UK261: a recommended act-by date (flight date + 12 months), the legal time-limit guidance, and an evidence checklist. Use for 'how long do I have to claim?'. Do NOT use to check eligibility; use check_compensation.

Input parameters:

- `flight_date` (string, required): Date of the disrupted flight, YYYY-MM-DD, e.g. 2026-09-01
- `scheme` (string, required): EU261 (EU/EEA departure or EU carrier) or UK261 (UK departure or UK carrier); check_compensation tells you which.

Output parameters:

- `disclaimer` (string): Not-legal-advice disclaimer to show the user.
- `evidence_checklist` (array): Evidence to gather, one per entry.
- `flight_date` (string): Flight date as given, YYYY-MM-DD.
- `recommended_action_by` (string): Suggested claim-by date (flight + 12 months), YYYY-MM-DD.
- `scheme` (string): Scheme the guidance is for.
- `window_guidance` (string): Legal time-limit guidance for the scheme.

### `generate_claim_letter` (~372 tokens)

Generate claim letter

Draft a formal EU261/UK261 compensation claim letter (subject, legal basis, amount, 14-day payment request, escalation notice) for the passenger to send themselves, plus sending tips. Nothing is sent. Use after check_compensation and pass its amount. Do NOT use to check eligibility; use check_compensation.

Input parameters:

- `airline_name` (string, required): Operating airline, e.g. "British Airways"
- `arrival` (string, required): Arrival airport 3-letter IATA code, case-insensitive, e.g. JFK
- `booking_reference` (string): Booking/PNR reference, e.g. ABC123. Optional.
- `claimed_amount` (number): Amount claimed, e.g. 600. If omitted, computed from the route like check_compensation (EUR 250/400/600 or GBP 220/350/520 by distance); required if an airport is unknown.
- `currency` (string): Currency of the claim. Default GBP for UK261, EUR for EU261.
- `departure` (string, required): Departure airport 3-letter IATA code, case-insensitive, e.g. LHR
- `flight_date` (string, required): Scheduled flight date, YYYY-MM-DD, e.g. 2026-09-01
- `flight_number` (string, required): Flight number, e.g. BA117
- `incident_summary` (string): One sentence on what happened, e.g. "the flight arrived 4 hours late due to a technical fault". Default generic wording.
- `passenger_name` (string, required): Passenger's full name as on the booking, e.g. "Jane Smith"
- `scheme` (string): Legal basis. Default: UK261 if departing the UK, else EU261 (without claimed_amount, worked out from the route; errors if neither applies).

Output parameters:

- `claimed_amount` (object): Amount and currency claimed.
- `disclaimer` (string): Not-legal-advice disclaimer to show the user.
- `letter` (string): Full letter text, ready to copy and send.
- `scheme` (string): Legal basis used in the letter.
- `sending_tips` (array): Practical tips for sending and follow-up.
- `subject` (string): Suggested email or letter subject line.

## Diagnostics

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

## Score history

- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 74
- 2026-10-12: 73
- 2026-10-10: 72
- 2026-10-09: 73
- 2026-10-04: 66

## Common questions

### What is the FlightFix MCP server?

FlightFix is an MCP server listed in the public MCP registry as io.github.everyai-com/flight-fix. EU261/UK261 flight compensation check, rights and claim letters. Free. This page covers its hosted endpoint (https://flight-fix.magicteams.ai/mcp).

### Is the FlightFix MCP server safe to use?

FlightFix scores 78 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 FlightFix MCP server expose?

FlightFix exposes 5 tools: check_compensation, compensation_table, disruption_rights, claim_timeline, generate_claim_letter. Their descriptions and schemas cost roughly 1,265 tokens of context every time the server is loaded.

### Does the FlightFix MCP server require authentication?

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

### Is the FlightFix MCP server still maintained?

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

## Links

- Remote endpoint: https://flight-fix.magicteams.ai/mcp
- Repository: https://github.com/everyai-com/sahadeva
- Changelog RSS feed: https://verifymcp.io/servers/everyai-com-flight-fix/flight-fix.xml
- Changelog JSON feed: https://verifymcp.io/servers/everyai-com-flight-fix/flight-fix.json
- HTML version of this page: https://verifymcp.io/servers/everyai-com-flight-fix/flight-fix