Flightaware
NPM · @PIPEWORX/MCP-FLIGHTAWARE · 2 COMPONENTS
FlightAware MCP — wraps FlightAware AeroAPI v4 (aeroapi.flightaware.com)
Available components
Last scanned (16 hours ago)
Scores higher than 72% 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-flightaware). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 894 tokens (~223/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 +26
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 2 Nov 26 −24
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Dependency health: pass → unverified ▼ functional
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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-flightaware@0.2.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-flightaware |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-flightaware/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637316670 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:efd5bb9f28de06c791cf1af3a51739f6476f6e637d43733632f7b49aa6c40e54e92009a5a4a3aa3a4e42b9dbe76a64f1b7adde0ac43aa9b7a375af72f |
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 →
flightaware_airport_flights ~241
List flights at an airport — arrivals and/or departures with scheduled & actual times. The `id` is an airport code (ICAO like "KSFO" or IATA like "SFO"). Use `type` to pick "arrivals", "departures", or "all" (default "all", which also includes scheduled flights). Example: flightaware_airport_flights({ id: "KSFO", type: "departures", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your FlightAware AeroAPI key |
| end | string | – | Optional ISO8601 date/time upper bound. |
| id | string | yes | Airport code — ICAO (e.g. "KSFO", "EGLL") or IATA (e.g. "SFO", "LHR"). |
| start | string | – | Optional ISO8601 date/time lower bound. |
| type | string | – | Which flights to return: "arrivals", "departures", or "all" (default). "all" hits the combined endpoint and returns arrivals, departures, scheduled_arrivals and scheduled_departures. |
No output schema declared.
No examples provided.
flightaware_flight_position ~147
Get the current/last-known position of an in-air flight: latitude, longitude, altitude, groundspeed, heading and timestamp. The `id` must be an AeroAPI fa_flight_id (from flightaware_flight_status). Example: flightaware_flight_position({ id: "UAL123-1234567890-airline-0123", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your FlightAware AeroAPI key |
| id | string | yes | AeroAPI fa_flight_id (from flightaware_flight_status). A bare flight number/tail number will NOT work here — this endpoint needs the fa_flight_id. |
No output schema declared.
No examples provided.
flightaware_flight_status ~257
Get real-time flight status for a flight number or tail number: origin/destination airports, scheduled/estimated/actual departure & arrival times, current status, and aircraft type. Returns a flights[] array (one flight ident can map to several dated flights). Example: flightaware_flight_status({ ident: "UAL123", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your FlightAware AeroAPI key (https://www.flightaware.com/aeroapi/signup/) |
| end | string | – | Optional ISO8601 date/time upper bound. |
| ident | string | yes | Flight identifier — airline flight number (ICAO preferred, e.g. "UAL123" for United 123) or aircraft registration / tail number (e.g. "N12345"). |
| ident_type | string | – | Optional. How to interpret `ident`: "designator" (flight number), "registration" (tail number), or "fa_flight_id". Omit to let AeroAPI infer. |
| start | string | – | Optional ISO8601 date/time lower bound, e.g. "2026-07-01" or "2026-07-01T00:00:00Z". |
No output schema declared.
No examples provided.
flightaware_flight_track ~197
Get the historical position track (breadcrumb trail of lat/lon/altitude/groundspeed points) for a specific flight. The `id` must be an AeroAPI fa_flight_id (e.g. "UAL123-1234567890-airline-0123") — get one from flightaware_flight_status first (the fa_flight_id field). Example: flightaware_flight_track({ id: "UAL123-1234567890-airline-0123", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your FlightAware AeroAPI key |
| id | string | yes | AeroAPI fa_flight_id (from flightaware_flight_status). A bare flight number/tail number will NOT work here — this endpoint needs the fa_flight_id. |
| include_estimated_positions | boolean | – | Optional. Include estimated positions where actual data is missing (default false). |
No output schema declared.
No examples provided.
How do I install the Flightaware MCP server?
Flightaware runs locally as an npm package, launched with npx -y @pipeworx/mcp-flightaware. 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-flightaware
claude mcp add pipeworx-io-flightaware -- npx -y @pipeworx/mcp-flightaware
What is the Flightaware MCP server?
Flightaware is an MCP server listed in the public MCP registry as io.github.pipeworx-io/flightaware. FlightAware MCP, wraps FlightAware AeroAPI v4 (aeroapi.flightaware.com). This page covers its npm package (@pipeworx/mcp-flightaware).
Is the Flightaware MCP server safe to use?
Flightaware scores 82 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 Flightaware MCP server expose?
Flightaware exposes 4 tools: flightaware_flight_status, flightaware_flight_track, flightaware_airport_flights, flightaware_flight_position. Their descriptions and schemas cost roughly 842 tokens of context every time the server is loaded.
Is the Flightaware MCP server still maintained?
Flightaware 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 Flightaware MCP server under?
Flightaware declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Flightaware MCP server?
VerifyMCP ran 16 checks on Flightaware, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.