Opensky
NPM · @PIPEWORX/MCP-OPENSKY · 2 COMPONENTS
OpenSky MCP — live aircraft, served from keyless community ADS-B feeds.
Available components
Last scanned (13 hours ago)
Scores higher than 77% 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-opensky). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- 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. 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 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.20 ▲ functional
- Package version: 0.2.0 → 0.2.1 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-opensky@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-opensky |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-opensky/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685160132 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7d5b4bffd457c8f4359d1fa749e5808c4578a46053b0f210fb1b76d8f8824228d420ffe2f28fe0f4e6687ab1ef7ce538841aadf305b1296ed1cb79d03 |
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 →
airspace_activity ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | yes | Region name, case-insensitive. For a custom area use opensky_get_states with lat/lon/radius_nm. |
No output schema declared.
No examples provided.
get_aircraft ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | ICAO24 transponder address in hex (e.g. "3c675a"). |
No output schema declared.
No examples provided.
get_flights ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| begin | number | yes | Start of the interval, Unix seconds. |
| end | number | yes | End of the interval, Unix seconds. |
No output schema declared.
No examples provided.
get_states ~197
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-opensky
claude mcp add pipeworx-io-opensky -- npx -y @pipeworx/mcp-opensky
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.