Live flight status, airport boards, aircraft lookups and what is overhead, from PlaneTrack.ai.
Scored across 10 tools
aircraft_overhead and live_aircraft_near are essentially the same operation (currently airborne aircraft within radius_km of a lat/lon, nearest first), differing only in credit cost, radius cap, and a few extra fields, so an agent has no principled way to choose. aircraft_info's 'where it is now if flying' also bleeds into aircraft_track and flight_status, and flight_history vs flight_on_date overlap around per-day flight legs.
Nearly all tools use snake_case with a resource prefix (aircraft_*, flight_*, airport_*), which makes the surface readable and predictable. The exceptions are live_aircraft_near and overhead_summary, which break the prefix-first pattern and use different ordering conventions.
Ten tools is a well-scoped size for a flight-data server, covering live, historical, and aggregate views. The count is slightly inflated by the redundant overhead/live_aircraft_near pair, which could be collapsed into one tool with parameters.
Coverage spans aircraft lookup, live tracking, airport boards, flight status/history, per-day outcomes, and reliability aggregates, which handles most core workflows. Gaps remain around future/scheduled flight search and airport reference data, and the 7-day lookback on flight_on_date forces external workarounds for older dates.
An aircraft by registration (e.g. N12345, G-EUPT) or Mode-S hex (e.g. a1b2c3): type, operator, where it is now if flying, and its flights in the last 7 days. Free, no key.
Inputs: ident (required).
Aircraft flying right now within radius_km (max 30) of a latitude/longitude, nearest first: callsign, type, altitude, speed. Free, no key.
Inputs: lat (required), lon (required), radius_km.
Positions of one aircraft (Mode-S hex, e.g. a1b2c3) over the last minutes (5 to 1440). 20 credits.
Inputs: icao24 (required), minutes.
Live departures and arrivals board for an airport (ICAO like KJFK or IATA like JFK): flight, other airport, status, time. Free, no key.
Inputs: airport (required).
Past legs of a flight number/callsign as flown (e.g. UAL1, BAW117): dates, airports, times, aircraft. 20 credits.
Inputs: callsign (required), days, limit.
What happened to a flight on a given day within the last 7 days: departure and arrival airports, scheduled and actual take-off, delay in minutes, status, aircraft. Free, no key. Older dates: point the user to the flight record at the returned link.
Inputs: date (required), callsign (required).
On-time performance for a flight number, a route (e.g. KJFK-KLAX or JFK-LAX) or a departure airport over the last 7 to 90 days (US airspace, FAA SWIM). Give exactly one of flight, route, airport. 20 credits.
Inputs: days, route, flight, airport.
Live status of a flight that is in the air now, by callsign or flight number as broadcast (e.g. UAL1, BAW117, DAL2540): route, progress, altitude, speed and estimated arrival. Free, no key.
Inputs: callsign (required).
Aircraft currently airborne within radius_km of a latitude/longitude, nearest first, with callsign, altitude, heading, speed and type. 10 credits.
Inputs: lat (required), lon (required), limit, radius_km.
How many aircraft passed within km of a point over the last 1 to 3 days: passes per day, lowest pass, busiest hour (UTC), night passes, types, operators, rarest visitor. 20 credits.
Inputs: lat (required), lon (required), km, days.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Flight tracker: your trips, any flight's live status, routes, Starlink Wi-Fi checks and fares.
Live flight radar: real-time position of any aircraft transmitting ADS-B right now. Search by regist
Flights MCP — live aircraft tracking + aircraft/route registry
Live flight departures and airport information
Add one secure layer between your agents and this server.
