{
  "markdown": "# OpenSky MCP\n\nLive aircraft positions and airspace-activity summaries, keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Auth\n\nNone. No key, no signup.\n\n## What this pack actually calls\n\n**Not OpenSky.** OpenSky Network blackholes datacenter egress — the connection\nhangs with no response and no reset, from Cloudflare Workers and from a non-CF\nrelay alike, with valid OAuth2 credentials. It works from a residential IP,\nwhich is what makes it look fixable; it is not, and credentials do not change\nit. Do not spend time trying again.\n\nThe tools keep the OpenSky names because that is what agents reach for, and\nserve the same live picture from the keyless community ADS-B mirrors:\n[adsb.lol](https://api.adsb.lol) → [airplanes.live](https://api.airplanes.live)\n→ [adsb.fi](https://opendata.adsb.fi), tried in that order. Every response\ncarries a `source` field naming the mirror that answered and a `note` saying\nthe data is not OpenSky's.\n\nState vectors are returned in **OpenSky's field names and units** — metres and\nm/s, not readsb's feet and knots — so code written against the OpenSky shape\nkeeps working rather than silently misreading altitudes.\n\n## Tools\n\n| Tool | Call it as | Returns |\n|---|---|---|\n| `get_states` | `opensky_get_states` | Live state vectors, filtered by `icao24` or by `lat`/`lon`/`radius_nm` |\n| `get_aircraft` | `opensky_get_aircraft` | Where one aircraft is right now, by ICAO24 hex |\n| `get_flights` | `get_flights` | Historical flight legs — **not available**, returns an explicit not-available result naming what does work |\n| `airspace_activity` | `airspace_activity` | Aircraft count, country breakdown, altitude and airborne split over a named region |\n\nTwo of these names are also exported by other packs (`country-state-city` has\nits own `get_states`; `flights` and `adsb` both have `get_aircraft`), so on the\nfull catalog the gateway exposes this pack's as `opensky_*`. The middle column\nis what you actually call there. On a scoped connection — `/opensky/mcp` — the\nbare names work, because there is nothing to collide with.\n\n## What is not available, and why\n\nHistorical endpoints. The community mirrors are live-only, and OpenSky is the\nonly source of \"which airports did this aircraft fly between last Tuesday\".\n`get_flights` therefore returns `found: false` with a reason rather than\nanswering a past-window question with a live snapshot.\n\nThere is no global \"every aircraft right now\" query either — the mirrors serve\na circle around a point, so `get_states` needs either an `icao24` filter or a\nlocation. Called with neither, it says so and gives the arguments to retry with.\n\n## Coverage caveats\n\n- Receiver-based. Mid-ocean, and areas with few ground receivers, are thin.\n- Military and state aircraft routinely disable transponders, so\n  `airspace_activity` undercounts non-civilian traffic. Read it as a\n  civilian-aviation normalcy signal, not an order of battle.\n- Regions larger than the feeds can cover in one pass report\n  `coverage: \"partial\"`, and their counts are a **floor**, not a total.\n- `origin_country` is derived from the ICAO 24-bit address block, which is\n  allocated by country of registration — it is not transmitted by the aircraft.\n  Only blocks confirmed against live registrations are mapped (validated at\n  1,125 aircraft agreeing, 0 conflicts); anything else reports `unknown`\n  rather than guessing.\n\n## Related\n\n- `flights` — `get_flight_route` (callsign → airline and route),\n  `get_arrivals` / `get_departures` (live airport activity inferred from ADS-B)\n- `adsb` — the same mirror chain with readsb-native field names and units\n- `aviation-weather` — METAR/TAF/SIGMET for the airports involved\n- `faa-delays` — FAA ground stops and delay programs for US airports\n\n## Data sources\n\n- https://api.adsb.lol\n- https://api.airplanes.live\n- https://opendata.adsb.fi\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"opensky\": {\n      \"url\": \"https://gateway.pipeworx.io/opensky/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/opensky/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Opensky data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5943,
  "sha": "ea81897cf2102fb03ed7204b5499aef383fff3d643d3c259044e506f2cc3b4cc",
  "repo_slug": "pipeworx-io/mcp-opensky",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_opensky_967346a3/readme"
}