# Opensky (npm · @pipeworx/mcp-opensky)

OpenSky MCP — live aircraft, served from keyless community ADS-B feeds.

- Trust score: 83/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`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-opensky/opensky-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-opensky/opensky-mcp)
- npm · `@pipeworx/mcp-opensky`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-opensky/pipeworx-mcp-opensky.md), [page](https://verifymcp.io/servers/pipeworx-io-opensky/pipeworx-mcp-opensky)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-opensky`
- 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-opensky).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 688 tokens (~172/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 Opensky MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 67, −12)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] Package version: 0.2.0 → 0.2.1

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `get_states` (~197 tokens)

Live ADS-B state vectors for aircraft currently transmitting — position, barometric and geometric altitude (metres), velocity (m/s), heading, vertical rate, squawk, and on-ground flag, plus registration and aircraft type. Filter to specific aircraft with comma-separated ICAO24 hex addresses, or to an area with lat/lon and a radius. Keyless. Use for "where is this aircraft now", "what is transmitting near this point", "is anything squawking an emergency code here".

Input parameters:

- `icao24` (string): Filter by one or more ICAO24 hex addresses, comma-separated (e.g. "3c675a,a835af").
- `lat` (number): Centre latitude for an area query, degrees.
- `lon` (number): Centre longitude for an area query, degrees.
- `radius_nm` (number): Radius around lat/lon in nautical miles (1-250, default 100).

### `get_aircraft` (~160 tokens)

Look up one aircraft by its ICAO24 transponder address (hex, e.g. "3c675a") and return where it is right now: position, altitude, speed, heading, squawk, registration, type and operator. Keyless. Historical flight legs for an aircraft are not available from the live feeds — for the scheduled route a callsign flies, use get_flight_route in the flights pack.

Input parameters:

- `begin` (number): Ignored — retained for compatibility; the live feeds carry no history.
- `end` (number): Ignored — retained for compatibility; the live feeds carry no history.
- `icao24` (string, required): ICAO24 transponder address in hex (e.g. "3c675a").

### `get_flights` (~140 tokens)

Historical flight legs (departure and arrival airports) for a past time window. NOT AVAILABLE from a hosted environment: OpenSky is the only source of this data and it cannot be reached from cloud infrastructure, while the keyless ADS-B feeds that replace it carry live positions only. Returns an explicit not-available result naming what does work instead — live aircraft via get_states, a callsign's scheduled route via get_flight_route, and live airport activity via get_arrivals / get_departures in the flights pack.

Input parameters:

- `begin` (number, required): Start of the interval, Unix seconds.
- `end` (number, required): End of the interval, Unix seconds.

### `airspace_activity` (~139 tokens)

Summary of live flight activity over a named region — aircraft count, country-of-registration breakdown, average altitude, and airborne vs on-ground split. Built for "is this airspace still operating" questions (airspace closures, conflict zones, strait and corridor traffic). Keyless. Supported regions: Iran, Israel, Syria, Ukraine, Russia, Taiwan, North Korea, South China Sea, Yemen, Strait of Hormuz, Taiwan Strait, Red Sea, Saudi Arabia, Gulf of Aden, Lebanon.

Input parameters:

- `region` (string, required): Region name, case-insensitive. For a custom area use opensky_get_states with lat/lon/radius_nm.

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 67
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Opensky MCP server?

Opensky is an MCP server listed in the public MCP registry as io.github.pipeworx-io/opensky. OpenSky MCP, live aircraft, served from keyless community ADS-B feeds. This page covers its npm package (@pipeworx/mcp-opensky).

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

Opensky 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 Opensky MCP server expose?

Opensky exposes 4 tools: get_states, get_aircraft, get_flights, airspace_activity. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.

### Is the Opensky MCP server still maintained?

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

Opensky 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 Opensky MCP server?

VerifyMCP ran 16 checks on Opensky, 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-opensky
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-opensky
- Repository: https://github.com/pipeworx-io/mcp-opensky
- Website: https://pipeworx.io/packs/opensky
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-opensky/pipeworx-mcp-opensky.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-opensky/pipeworx-mcp-opensky/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-opensky/pipeworx-mcp-opensky.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-opensky/pipeworx-mcp-opensky