Summary
Per-aircraft history with the aggregates already worked out.
The per-year tools are the reason to use this rather than a tracking site: flights by year, by trip distance and by arrival country arrive as summaries instead of a list you have to count. FlightDB describes its source as unfiltered ADS-B Exchange data, so tails that consumer trackers suppress are present here.
What it is
A hosted server over FlightDB, which combines ADS-B Exchange flight data with official aircraft registry records. Streamable HTTP, and you sign in with Google once.
What you get
- Flight_list_flights: paginated flights filtered by aircraft, airport, country or date range
- Flight_list_aircraft: the aircraft directory, filtered by registration, country or ICAO type
- Flight_get_aircraft_from_list for a single aircraft header, Flight_get_aircraft_detail for the full profile with all flights and aggregates
- Flight_flights_by_year for per-year counts, Flight_flights_by_distance for those counts binned Short, Medium and Long, Flight_flights_by_country for the arrival-country breakdown
- Flight_airport_visits for per-airport visit and stay aggregates by year, Flight_visit_history for the timeline
- Flight_get_airport to resolve an IATA or ICAO code
Requirements
Nothing to install. Add https://flightdb.org/mcp as a custom connector in any client that speaks Streamable HTTP, then sign in with Google when prompted; the authorisation persists.
Setup effort
One command — npx -y mcp-remote https://flightdb.org/mcp