# Flightaware (npm · @pipeworx/mcp-flightaware)

FlightAware MCP — wraps FlightAware AeroAPI v4 (aeroapi.flightaware.com)

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-flightaware/flightaware-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-flightaware/flightaware-mcp)
- npm · `@pipeworx/mcp-flightaware`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-flightaware/pipeworx-mcp-flightaware.md), [page](https://verifymcp.io/servers/pipeworx-io-flightaware/pipeworx-mcp-flightaware)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-flightaware`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-flightaware).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add pipeworx-io-flightaware -- npx -y @pipeworx/mcp-flightaware
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-flightaware": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-flightaware"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-flightaware": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-flightaware"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-flightaware -- npx -y @pipeworx/mcp-flightaware
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-flightaware": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-flightaware"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-flightaware --command npx --arg -y --arg @pipeworx/mcp-flightaware
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-flightaware:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-flightaware"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-flightaware": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-flightaware"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-flightaware -t stdio -c npx -a -y @pipeworx/mcp-flightaware
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-flightaware": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-flightaware"
      ]
    }
  }
}
```

## 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-11-05 (score 82, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 82, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-03 (score 81, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-02 (score 55, −24)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `flightaware_flight_status` (~257 tokens)

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" })

Input parameters:

- `_apiKey` (string, required): Your FlightAware AeroAPI key (https://www.flightaware.com/aeroapi/signup/)
- `end` (string): Optional ISO8601 date/time upper bound.
- `ident` (string, required): 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".

### `flightaware_flight_track` (~197 tokens)

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" })

Input parameters:

- `_apiKey` (string, required): Your FlightAware AeroAPI key
- `id` (string, required): 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).

### `flightaware_airport_flights` (~241 tokens)

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" })

Input parameters:

- `_apiKey` (string, required): Your FlightAware AeroAPI key
- `end` (string): Optional ISO8601 date/time upper bound.
- `id` (string, required): 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.

### `flightaware_flight_position` (~147 tokens)

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" })

Input parameters:

- `_apiKey` (string, required): Your FlightAware AeroAPI key
- `id` (string, required): 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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-flightaware/pipeworx-mcp-flightaware#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 55
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-flightaware
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-flightaware
- Repository: https://github.com/pipeworx-io/mcp-flightaware
- Website: https://pipeworx.io/packs/flightaware
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-flightaware/pipeworx-mcp-flightaware.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-flightaware/pipeworx-mcp-flightaware/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-flightaware/pipeworx-mcp-flightaware.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-flightaware/pipeworx-mcp-flightaware