Airspace

Airspace — connector documentation

• MCP endpoint: https://airspace.connectorbay.com/mcp
• REST API: POST https://airspace.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://airspace.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://airspace.connectorbay.com/health · Tool schemas: https://airspace.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/airspace · agent@connectorbay.com

What Airspace is for

Aviation questions answered from the sources pilots and dispatchers use, decoded so an assistant can speak plainly: what the weather is at an airport right now and what the forecast says for tonight, whether it is VFR or IFR, whether there is a ground stop at Newark, what turbulence pilots are reporting near Denver, how long Aspen's runway is and what its tower frequency is, what aircraft are overhead, and where a particular flight is at this moment.

What it does

METARs decoded into wind, visibility, weather, clouds, ceiling, temperature and altimeter, with the flight category explained and a one-line summary — any airport worldwide. TAFs decoded period by period. Active SIGMETs, convective SIGMETs and G-AIRMETs over or near a point (point-in-polygon), and pilot reports within a radius. FAA ground stops, ground delay programs, arrival/departure delays and closures for one U.S. airport or nationwide. Airport details: codes, runways (length, width, surface), frequencies, tower, elevation, magnetic variation, Wikipedia link, plus name/city search over 6,145 airports. Live aircraft near a place with distance and bearing; a flight by callsign, registration or hex with registry details and community-reported route; emergency squawks; military aircraft airborne. A briefing tool assembles departure, destination and alternate weather, en-route advisories, PIREPs, FAA status and the great-circle distance in one call.

What it is not

Airspace is not an official weather briefing or a flight-planning tool; before a flight, pilots must obtain a briefing from Flight Service or an approved provider. Live positions come from volunteer ADS-B receivers (adsb.lol) and can lag or miss aircraft — absence in the feed does not mean absence in the sky. FAA status covers U.S. airports only; SIGMET/G-AIRMET coverage is U.S. and adjacent airspace. Community route data for a callsign can be stale.

Tools

Weather

metar — Current weather at an airport: the METAR decoded — wind, visibility, weather, clouds and ceiling, temperature/dew point, altimeter — with the flight category (VFR/MVFR/IFR/LIFR) explained and a one-line plain-English summary, plus the raw report. Any airport worldwide that reports METARs. Use for "weather at SFO", "is JFK IFR right now". Args: airports, hours.

taf — Terminal forecast (TAF) for an airport, decoded period by period — from/temporary/becoming/probability groups with wind, visibility, weather, clouds and ceiling in plain English — plus the raw TAF and validity window. Use for "will SFO be foggy tonight", "forecast for JFK this evening", "when does the wind shift at DEN". Args: airports.

hazards — Active SIGMETs, convective SIGMETs and G-AIRMETs — thunderstorms, turbulence, icing, IFR, mountain obscuration, wind shear — over or within ~60 nm of an airport or place, with altitudes, validity, movement and the raw text. U.S. and adjacent airspace (NOAA AWC). Use for "any turbulence advisories near Denver", "convective SIGMETs right now", "is there icing forecast over the Rockies". Args: airport, place, latitude, longitude, hazard, all_active.

pireps — Recent pilot reports (PIREPs) near an airport: turbulence and icing intensity, cloud tops/bases, weather, wind and temperature aloft, with aircraft type and flight level. U.S. coverage. Use for "any turbulence reported near Denver", "what are pilots reporting around ORD". Args: airport, distance_sm, hours.

Airports

airport — Airport details: name, codes (ICAO/IATA/FAA), location and elevation, runways with length, width and surface, control tower, radio frequencies (ATIS, ground, tower, approach), magnetic variation, type and Wikipedia link — or a search by name/city returning candidates. Use for "how long is the runway at Aspen", "tower frequency at SFO", "what's the airport code for Bengaluru". Args: code, search.

airport_status — FAA airport status right now: ground stops, ground delay programs (average/max delay), arrival and departure delays with trend, and closures with reopen times — for one U.S. airport or all airports currently affected. Use for "any delays at Newark", "is there a ground stop at JFK", "which airports have delays right now". Args: airport.

Live aircraft

aircraft_nearby — Aircraft currently in the air near a place (community ADS-B): callsign, registration, type, altitude, speed, heading, climb/descent, distance and bearing from the point, squawk and any emergency. Use for "what planes are overhead", "what's flying near SFO", "is anything circling over downtown". Args: place, latitude, longitude, radius_nm, airborne_only, max_results.

track_flight — Where a flight or aircraft is right now: position, altitude, speed, heading, vertical rate, squawk, nearest airport, plus the aircraft's registration, type and owner (hexdb) and the community-reported route for the callsign. Only aircraft currently transmitting are found. Use for "where is UA604", "track N215UA", "what is hex a1cdd8". Args: query.

aircraft_lookup — What an aircraft is, from its registration or hex code: manufacturer, type, registered owner/operator — and whether it is airborne right now (position if so). Use for "what plane is N215UA", "who owns hex a1cdd8". Args: query.

special_traffic — Aircraft squawking an emergency right now (7700 general, 7600 radio failure, 7500 hijack) or military aircraft currently airborne (optionally near a place), with position, altitude, type and callsign. Use for "is any plane declaring an emergency", "military aircraft over the North Sea". Args: kind, near, max_results.

Combined

briefing — A quick weather and status briefing for a flight: current METAR and TAF at departure, destination (and alternate), flight categories, SIGMETs/G-AIRMETs over either end or along the straight-line route, recent PIREPs near each end, FAA delays/ground stops (U.S.), and the great-circle distance and bearing. Not an official briefing. Use for "brief me for SFO to LAX", "what's the weather for my flight from JFK to BOS". Args: departure, destination, alternate.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/airspace/support

Airspace — Privacy Policy

Effective 23 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Airspace is. Airspace is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for aviation information: airport weather and forecasts, weather advisories and pilot reports, FAA airport status, airport details, live aircraft positions and aircraft registry lookups. You interact with your assistant; the assistant sends us only the airport code, place, callsign or registration needed for the lookup.

What we receive. The arguments of each tool call (an airport code, a place name or coordinates, a callsign, registration or hex code), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Lookups are forwarded, not stored. Airport codes and callsigns are passed to the sources below and the answer is returned to your assistant. A place name is resolved to coordinates with a bundled gazetteer, or by Open-Meteo's geocoder when it is not in the bundle. Nothing you send is stored, logged in request bodies, profiled or used to train anything. Successful upstream answers are cached in memory for seconds to hours, keyed by the query, to reduce load on the sources.

What we do not receive or store. We do not receive your conversation with the assistant, your name, contacts, accounts or credentials for any service, or your own location unless the assistant sends coordinates for a "what's overhead" question — and those are used for that one lookup only. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. The query is sent to the relevant source: NOAA Aviation Weather Center (aviationweather.gov) for METAR/TAF/SIGMET/PIREP and airport data, FAA NAS Status (nasstatus.faa.gov) for airport delays, adsb.lol for live aircraft, hexdb.io for aircraft registry and routes, and Open-Meteo for geocoding of place names. Each receives the query and our server's IP address, never yours. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Airspace is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Airspace — Terms of Service

Effective 23 September 2026. These terms govern use of the Airspace connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Airspace returns aviation weather (METAR, TAF, SIGMET/AIRMET, PIREP), FAA airport status, airport details, live aircraft positions from community ADS-B feeds and aircraft registry data. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Not an official briefing. Weather and advisory data are relayed from NOAA and the FAA for situational awareness only. They are not a flight-planning service or a substitute for a preflight briefing from Flight Service or an approved provider, and must not be used as the sole basis for any operational decision.
3. Live positions. Aircraft positions come from volunteer ADS-B receivers (adsb.lol) and may be delayed, incomplete or wrong; military and blocked aircraft may be absent. Do not rely on them for safety, security or legal purposes.
4. Sources. NOAA Aviation Weather Center and FAA NAS Status (U.S. government, public domain), adsb.lol (community, non-commercial), hexdb.io, OurAirports (public domain), GeoNames (CC BY) and Open-Meteo. We do not control these sources.
5. Acceptable use. Do not use the Service to overwhelm the underlying services or to circumvent rate limits. Automated use within the published limits is welcome; bulk redistribution of adsb.lol data is not.
6. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
7. Data. Our Privacy Policy describes what we process. In short: your query is forwarded to the sources and nothing is stored.
8. Attribution. NOAA Aviation Weather Center; FAA; adsb.lol; hexdb.io; OurAirports; GeoNames; Open-Meteo.
9. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/airspace

Airspace support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://airspace.connectorbay.com/mcp
• REST API: https://airspace.connectorbay.com/openapi.json
• Live status: https://airspace.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Airspace never asks for them.