Flights
NPM · @PIPEWORX/MCP-FLIGHTS · 2 COMPONENTS
Flights MCP — live aircraft tracking + aircraft/route registry
Available components
Last scanned (1 hour ago)
Scores higher than 76% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-flights). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1103 tokens (~220/item across 5 items; 5 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 Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 1.1.0 → 1.1.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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 · Analysed npm/@pipeworx/mcp-flights@1.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-flights |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-flights/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637316749 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:12c9e0f7a3246b3f568de874ce5d860eb497bac0325f2519648f87591bce6956ae783a611db0d0dafbce5a46c7a6f5e8b8369a5f30398ca72ec3f7b6c |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_aircraft ~139
Look up ONE aircraft by ICAO24 transponder hex (e.g. "a4d97e"). Returns registry details — registration/tail number, manufacturer, type, and registered owner/operator — plus its LIVE position if it is currently transmitting. No key required. Use for "what is aircraft <hex>", "who operates <hex>", "where is <hex> now". If you only have a flight number/callsign, use get_flight_route instead.
| Name | Type | Req | Description |
|---|---|---|---|
| icao24 | string | yes | ICAO24 transponder address — 6 hex characters, e.g. "a4d97e" (case-insensitive) |
No output schema declared.
No examples provided.
get_arrivals ~274
Aircraft currently ARRIVING at an airport — live ADS-B, no key required. Pass an ICAO code (e.g. "KSFO", "EGLL") and get inbound traffic descending toward the field, nearest first, with callsign, registration, aircraft type, altitude, descent rate and distance out. Use for "what is landing at <airport> right now", "inbound traffic to <airport>". This is a live picture, not a scheduled timetable. (Historical windows via begin/end require OpenSky credentials and only work when self-hosting — OpenSky is unreachable from cloud egress.)
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | ICAO airport code, e.g. "KJFK", "EGLL", "KSFO" (4 letters, not the 3-letter IATA code) |
| begin | number | – | OPTIONAL historical window start (Unix seconds). Requires OpenSky credentials and only works when self-hosting; omit for live data. |
| end | number | – | OPTIONAL historical window end (Unix seconds, max 7 days after begin). Omit for live data. |
| limit | number | – | Max aircraft to return (1-200, default 50), nearest first. |
| radius_nm | number | – | How far out to look, nautical miles (1-250, default 40). |
No output schema declared.
No examples provided.
get_departures ~273
Aircraft currently DEPARTING an airport — live ADS-B, no key required. Pass an ICAO code (e.g. "KSFO", "EGLL") and get outbound traffic climbing out of the field, nearest first, with callsign, registration, aircraft type, altitude, climb rate and distance out. Use for "what just took off from <airport>", "outbound traffic from <airport>". This is a live picture, not a scheduled timetable. (Historical windows via begin/end require OpenSky credentials and only work when self-hosting — OpenSky is unreachable from cloud egress.)
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | ICAO airport code, e.g. "KJFK", "EGLL", "KSFO" (4 letters, not the 3-letter IATA code) |
| begin | number | – | OPTIONAL historical window start (Unix seconds). Requires OpenSky credentials and only works when self-hosting; omit for live data. |
| end | number | – | OPTIONAL historical window end (Unix seconds, max 7 days after begin). Omit for live data. |
| limit | number | – | Max aircraft to return (1-200, default 50), nearest first. |
| radius_nm | number | – | How far out to look, nautical miles (1-250, default 40). |
No output schema declared.
No examples provided.
get_flight_route ~139
Resolve a flight callsign / flight number (e.g. "UAL1", "BAW117") to its airline and scheduled ROUTE — origin and destination airports with names, IATA/ICAO codes, and coordinates. No key required. Use for "where does flight X fly from/to", "what route is <callsign>", "which airline is <callsign>". Complements get_flights_in_area, which gives you callsigns of aircraft currently overhead.
| Name | Type | Req | Description |
|---|---|---|---|
| callsign | string | yes | Flight callsign, ICAO or IATA form (e.g. "UAL1", "UA1", "BAW117") |
No output schema declared.
No examples provided.
get_flights_in_area ~227
Find aircraft currently airborne in a geographic area, by bounding box. LIVE ADS-B data, no key required. Returns per aircraft: ICAO24 hex, callsign, registration (tail number), aircraft type, position, altitude, ground speed, heading, vertical rate, squawk, and any emergency code. Use for "what planes are over <place> right now", "aircraft near <airport>", "is anything squawking 7700 near X". For one known aircraft use get_aircraft; for what route a callsign flies use get_flight_route.
| Name | Type | Req | Description |
|---|---|---|---|
| lamax | number | yes | Maximum (north) latitude of the bounding box, degrees |
| lamin | number | yes | Minimum (south) latitude of the bounding box, degrees |
| limit | number | – | Max aircraft to return (1-500, default 200), nearest the box centre first. |
| lomax | number | yes | Maximum (east) longitude of the bounding box, degrees |
| lomin | number | yes | Minimum (west) longitude of the bounding box, degrees |
No output schema declared.
No examples provided.
How do I install the Flights MCP server?
Flights runs locally as an npm package, launched with npx -y @pipeworx/mcp-flights. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-flights
claude mcp add pipeworx-io-flights -- npx -y @pipeworx/mcp-flights
What is the Flights MCP server?
Flights is an MCP server listed in the public MCP registry as io.github.pipeworx-io/flights. Flights MCP, live aircraft tracking + aircraft/route registry. This page covers its npm package (@pipeworx/mcp-flights).
Is the Flights MCP server safe to use?
Flights scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Flights MCP server expose?
Flights exposes 5 tools: get_flights_in_area, get_aircraft, get_flight_route, get_arrivals, get_departures. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.
Is the Flights MCP server still maintained?
Flights 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 licence is the Flights MCP server under?
Flights declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.