# FlightFix

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

- name: io.github.everyai-com/flight-fix
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 90/100 flags: duplicate-repo
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Fflight-fix
- tools: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Fflight-fix/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 99
- freshness: 100
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-97% +updated-16d-ago -duplicate-repo(15 names)
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list carries no ttlMs, so clients re-fetch it

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,783 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 13 tool changes in 30 days
- fail `stability.rug_pull`: 10 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 1,783 tokens to load them all
- tool set hash: 23b43de4cfa6ab2a0d3a8073eeaa1edf
- tools last changed: 2026-10-10T21:31:17.058Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.everyai-com/flight-fix.svg)](https://protogrid.dev/servers/io.github.everyai-com/flight-fix)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-10 `generate_claim_letter` changed (inputSchema)
- 2026-10-10 `disruption_rights` changed (description, inputSchema, outputSchema)
  - before: List the EU261/UK261-style passenger rights for a disruption type (refund or re-routing, care by distance band, 5-hour refund option, denied-boarding rules, payment terms) plus the complaint escalation path. It does not check whether EU261/UK261 covers the route or compute money owed; use check_compensation for that.
  - after: 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.
- 2026-10-10 `check_compensation` changed (outputSchema)
- 2026-10-10 `generate_claim_letter` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Create a compensation claim letter for an airline delay/cancellation, using EU261/UK261. Use this when you need a formal letter to send to the airline. Do NOT use when you need to check eligibility first; use check_compensation instead.
  - after: 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.
- 2026-10-10 `claim_timeline` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Retrieve claim timeline for a flight date. Use when needing specific deadlines and evidence for EU261 or UK261 claims. Do NOT use for general disruption rights; use disruption_rights instead.
  - after: 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.
- 2026-10-10 `disruption_rights` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Retrieve flight disruption rights for a given flight. Use when needing specific rights for a disrupted flight; NOT for general compensation info. Use compensation_table instead.
  - after: List the EU261/UK261-style passenger rights for a disruption type (refund or re-routing, care by distance band, 5-hour refund option, denied-boarding rules, payment terms) plus the complaint escalation path. It does not check whether EU261/UK261 covers the route or compute money owed; use check_compensation for that.
- 2026-10-10 `compensation_table` changed (description, outputSchema, annotations) **meaning changed**
  - before: Retrieve EU261/UK261 compensation amounts by distance band. Use when needing specific compensation details for flights within the EU or UK. Do NOT use for non-EU/UK flights; use disruption_rights instead.
  - after: 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.
- 2026-10-10 `check_compensation` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Calculate EU261/UK261 compensation for a disrupted flight. Use this when you need to determine the compensation amount for a specific flight disruption. Do NOT use for general compensation rules; use disruption_rights instead.
  - after: 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.
- 2026-10-06 `generate_claim_letter` changed (title, description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Generate a formal compensation claim letter to the airline, citing EU261/UK261 with your flight details filled in.
  - after: Create a compensation claim letter for an airline delay/cancellation, using EU261/UK261. Use this when you need a formal letter to send to the airline. Do NOT use when you need to check eligibility first; use check_compensation instead.
- 2026-10-06 `claim_timeline` changed (title, description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Claim deadline guidance and evidence checklist for a flight date.
  - after: Retrieve claim timeline for a flight date. Use when needing specific deadlines and evidence for EU261 or UK261 claims. Do NOT use for general disruption rights; use disruption_rights instead.

Full history: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Fflight-fix/changes

## Remotes

- https://flight-fix.magicteams.ai/mcp (streamable-http, auth none, reachable true, uptime30d 0.96825397)

## Packages

_none_

## Tools (5)

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