# Airports (npm · @pipeworx/mcp-airports)

Airports MCP — wraps AirportGap API (free, no auth required), plus a D1 copy of the OurAirports…

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-airports`
- 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-airports).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1355 tokens (~169/item across 8 items; 8 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 Airports MCP server?

Airports runs locally as an npm package, launched with npx -y @pipeworx/mcp-airports. 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-airports -- npx -y @pipeworx/mcp-airports
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 84, +1)

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

### 2026-11-03 (score 83, +1)

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

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

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

### 2026-10-30 (score 81, +1)

- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (8)

### `search_airports` (~131 tokens)

Look up an airport by city name (e.g. "Tokyo", "New York", "London") OR by 3-letter IATA code (e.g. "JFK", "LHR"). City lookup uses a bundled map of the top ~150 international hubs; cities with multiple airports return all primary ones. For airports not in the bundle, pass an IATA code or use the aviationstack pack for full-text name/country search.

Input parameters:

- `query` (string, required): City name (e.g. "Chicago", "London") or 3-letter IATA code (e.g. "ORD")

### `get_airport` (~63 tokens)

Get airport details by IATA code (e.g., "JFK", "LHR"). Returns name, city, country, coordinates, altitude, timezone.

Input parameters:

- `iata_code` (string, required): Three-letter IATA airport code (e.g. "JFK")

### `calculate_distance` (~79 tokens)

Calculate straight-line distance between two airports by IATA code (e.g., "JFK" to "LHR"). Returns kilometers and miles.

Input parameters:

- `from` (string, required): IATA code of the origin airport (e.g. "JFK")
- `to` (string, required): IATA code of the destination airport (e.g. "LHR")

### `ourairports_lookup` (~273 tokens)

Look up ANY airfield in the OurAirports bulk dataset (~86,000 rows: every ICAO/IATA/local-code airport, heliport, seaplane base and balloonport OurAirports tracks, including fields with no IATA code at all). Pass ANY of: an ICAO code ("KJFK", "EGLL"), an IATA code ("JFK"), a GPS code, or OurAirports' own local/national ident (e.g. a US local code like "00A", or a non-US ident like "AT-0001"). Returns name, type (large_airport/medium_airport/small_airport/heliport/seaplane_base/balloonport/closed), coordinates, elevation, country/region, and whether it has scheduled airline service. This is the superset of get_airport's AirportGap data -- use this for any code AirportGap does not recognize, or for a heliport/seaplane base/ICAO-only field get_airport cannot see at all. An unrecognized code is refused with a clear error, never an empty success.

Input parameters:

- `code` (string, required): ICAO code ("KJFK"), IATA code ("JFK"), GPS code, or OurAirports local ident (e.g. "00A").

### `airport_runways` (~161 tokens)

Runway details for one airfield from the OurAirports dataset: for each runway, length and width in feet, surface type, whether it is lighted, whether it is closed, and both ends' ident/coordinates/elevation/heading/displaced threshold. Pass any code ourairports_lookup accepts (ICAO, IATA, GPS or local ident). An airfield with no fixed-wing runways on file (e.g. most heliports) returns an empty runways array with found:true, not an error. An unrecognized airfield code is refused with a clear error, never an empty success.

Input parameters:

- `code` (string, required): ICAO/IATA/GPS/local code, e.g. "KJFK" or "JFK".

### `airport_frequencies` (~131 tokens)

Radio frequencies for one airfield from the OurAirports dataset: type (ATIS/TWR/GND/CLD/DIR/APP/DEP/CTAF/UNICOM/...), a human description, and the frequency in MHz. Pass any code ourairports_lookup accepts. An airfield with no frequencies on file returns an empty list with found:true, not an error. An unrecognized airfield code is refused with a clear error, never an empty success.

Input parameters:

- `code` (string, required): ICAO/IATA/GPS/local code, e.g. "EGLL" or "LHR".

### `airport_navaids` (~149 tokens)

Navigational aids (NDB, VOR, DME, VOR-DME, VORTAC, TACAN, ...) associated with one airfield from the OurAirports dataset: ident, name, type, frequency in kHz, coordinates, elevation, DME channel and power. Pass any code ourairports_lookup accepts. Most airfields have none on file (navaids are sparse relative to airports) -- that returns an empty list with found:true, not an error. An unrecognized airfield code is refused with a clear error, never an empty success.

Input parameters:

- `code` (string, required): ICAO/IATA/GPS/local code, e.g. "KORD".

### `ourairports_search` (~317 tokens)

Search the OurAirports dataset (~86,000 airfields) by a text match against name, municipality or ident, optionally narrowed by ISO country code (e.g. "US", "GB") and/or airfield type ("large_airport", "medium_airport", "small_airport", "heliport", "seaplane_base", "balloonport", "closed"). Results default to airfields with scheduled airline service first. Use this to find airfields by partial name/city when you do not already have a code -- ourairports_lookup requires an exact code. Rows beyond `limit` are reported via truncated/total_matching rather than silently dropped -- narrow the query or page with limit/offset to see the rest. A query that matches nothing returns found:false with an explanation, never a silent empty array mistaken for "no such place".

Input parameters:

- `country` (string): Optional: ISO 3166-1 alpha-2 country code, e.g. "US", "GB", "FR".
- `limit` (number): Max rows to return, 1-100. Default 20. A truncated response carries truncated:true and total_matching.
- `offset` (number): Pagination offset. Default 0.
- `query` (string): Text to match against name, municipality or ident, e.g. "Heathrow" or "Bensalem".
- `type` (string): Optional: airfield type, e.g. "heliport", "small_airport", "large_airport".

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80

## Common questions

### What is the Airports MCP server?

Airports is an MCP server listed in the public MCP registry as io.github.pipeworx-io/airports. Airports MCP, wraps AirportGap API (free, no auth required), plus a D1 copy of the OurAirports… This page covers its npm package (@pipeworx/mcp-airports).

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

Airports scores 84 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 Airports MCP server expose?

Airports exposes 8 tools: search_airports, get_airport, calculate_distance, ourairports_lookup, airport_runways, and 3 more. Their descriptions and schemas cost roughly 1,304 tokens of context every time the server is loaded.

### Is the Airports MCP server still maintained?

Airports 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 Airports MCP server under?

Airports declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

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