F
licenseA
qualityC
maintenanceAn MCP server for live flight tracking and real-time status checks, including airport and airline code resolution, powered by the free AviationStack API.
4
-
flightaware-mcp
by chrischall
Related Servers
Alternatives to flightaware-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceA Model Context Protocol (MCP) server that provides real-time flight tracking and status information using the AviationStack API.35,978 npm7MIT
- AlicenseNot gradedqualityCmaintenanceProvides comprehensive flight tracking capabilities using the OpenSky Network API, enabling real-time flight data, geographic searches, historical data, and airport operations through MCP tools.MIT
- AlicenseBqualityBmaintenanceA Claude Desktop MCP server that helps you track flights in real-time using Flightradar24 data. Perfect for aviation enthusiasts, travel planners, or anyone curious about flights overhead!215 npm47MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for flight schedule finding via Skyscanner API. Enables querying flight quotes and schedules using natural language.-
- AlicenseNot gradedqualityCmaintenanceMCP server providing real-time aviation weather data (METAR, TAF, PIREPs, AIRMETs) from aviationweather.gov for flight planning and analysis.14 npmMIT
TDQS
A3.9/5.0
Scored across 34 tools
Disambiguation4/5
The five search-style tools (fa_search_flights, fa_search_flights_advanced, fa_search_flight_positions, fa_count_flights, fa_foresight_search) plus fa_get_flights and fa_get_flight_history genuinely overlap in purpose, and the two different query grammars are easy to mix up. Descriptions are unusually explicit about the distinctions (simplified vs structured syntax, positions vs summaries, predicted vs live), which mitigates most confusion.
Naming Consistency5/5
Every tool uses a consistent fa_ verb_noun snake_case pattern (fa_get_*, fa_search_*, fa_list_*, fa_create_*, fa_resolve_*). Resource prefixes are applied uniformly across flights, airports, operators, and alerts, so the naming is highly predictable.
Tool Count3/5
34 tools is heavy and sits in the oversized band, with a sizable alerts sub-cluster (7 tools) and a dense flight-search cluster. The underlying domain (flights, airports, operators, alerts) is genuinely large, so the count is defensible but still on the bloated side.
Completeness5/5
Coverage is comprehensive: full CRUD for alerts plus endpoint management, complete flight/airport/operator read surfaces with weather, delays, routes, counts, and search. No obvious lifecycle gaps, and limits (tier requirements, confirmation flows) are documented inline.
Maintenance
ActivityActive
ResponsivenessWithin a week