Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
Directory / flight-data
flight-data
by planetrack.ai · https://planetrack.ai/mcp
Live flight status, airport boards, aircraft lookups and what is overhead, from PlaneTrack.ai.
11 of 11 checks · 10 Nov 2026
At a glance
- Runs where
- On their server. What you send to it goes to them.
- What you need
- Nothing: it answered without a login
- Tools
- 10 tools
- Its own safety labels
- 5 read-only, 5 with no label
- Memory it takes
- About 1,000 tokens of your AI's memory, just for its tool descriptions
- Largest answer
- About 0.2 KB in our test
- Speed
- Average answer in our test: 233 ms
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 10 Nov 2026.
Is flight-data MCP server safe?
- None of the hidden-instruction wordings we know were found in its 10 tool descriptions.
- Its error messages showed no secrets or internal details.
- 5 of its 10 tools are labeled read-only; the others may change or send things.
- Overall it scored 73/100 on 10 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
- Its source code and packages.
- What a tool quietly does behind the scenes, such as writing a file or calling another service.
- Instructions hidden inside live tool answers. We only look for those in tool descriptions.
- Hidden instructions worded in a way our list doesn't know yet.
- Tools that could change something. Those are read, never run.
What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection
Known security advisories
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
10 tools, in the server's own words.
flight_statusread-onlyLive status of a flight that is in the air now, by callsign or flight number as broadcast (e.g.
flight_on_dateread-onlyWhat 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, aircr…
airport_boardread-onlyLive departures and arrivals board for an airport (ICAO like KJFK or IATA like JFK): flight, other airport, status, time.
aircraft_inforead-onlyAn aircraft by registration (e.g.
aircraft_overheadread-onlyAircraft flying right now within radius_km (max 30) of a latitude/longitude, nearest first: callsign, type, altitude, speed.
live_aircraft_nearAircraft currently airborne within radius_km of a latitude/longitude, nearest first, with callsign, altitude, heading, speed and type.
aircraft_trackPositions of one aircraft (Mode-S hex, e.g.
flight_historyPast legs of a flight number/callsign as flown (e.g.
flight_reliabilityOn-time performance for a flight number, a route (e.g.
overhead_summaryHow 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, rares…
Test results
Safe mode: only tools labeled read-only were run. How the test works
- !Ready for the newest MCP versionnote
1 warning
- !Uses an older MCP version (2025-06-18). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
- !Every tool is describednote
8 warnings
- !airport_board: Inputs with no description: airport
- !aircraft_info: Inputs with no description: ident
- !aircraft_overhead: Inputs with no description: lat, lon, radius_km
- !live_aircraft_near: Inputs with no description: lat, lon, radius_km, limit
- !aircraft_track: Inputs with no description: icao24, minutes
- !flight_history: Inputs with no description: callsign, days, limit
- !flight_reliability: Inputs with no description: flight, route, airport, days
- !overhead_summary: Inputs with no description: lat, lon, km, days
- !Tools are labeled safe or dangerousnote
1 warning
- !5 of 10 tools have no safety label (read-only or dangerous): live_aircraft_near, aircraft_track, flight_history, flight_reliability, overhead_summary
- !Tools work with good inputsnote
1 warning
- !flight_on_date: Answered, but it gives the exact same answer to bad input as to good input, so it may be ignoring what it is sent
- –live_aircraft_near: Not run: no safety label (if you own this server, test again in owner mode)
- –aircraft_track: Not run: no safety label (if you own this server, test again in owner mode)
- –flight_history: Not run: no safety label (if you own this server, test again in owner mode)
- –flight_reliability: Not run: no safety label (if you own this server, test again in owner mode)
- –overhead_summary: Not run: no safety label (if you own this server, test again in owner mode)
- and 4 more
- !Bad inputs give a clean errornote
5 warnings
- !flight_status: Accepted missing required input "callsign" without complaining
- !flight_on_date: Accepted missing required input "callsign" without complaining
- !airport_board: Accepted missing required input "airport" without complaining
- !airport_board: Accepted wrong type for "airport" without complaining
- !aircraft_info: Accepted missing required input "ident" without complaining
- and 5 more
- !Follows MCP best practices (not scored yet)note
3 tips (not scored)
- !5 tools not labeled read-only don't say whether running them twice is safe (idempotentHint): live_aircraft_near, aircraft_track, flight_history, flight_reliability, overhead_summary
- !5 tools don't say whether they reach outside services like the web (openWorldHint): live_aircraft_near, aircraft_track, flight_history, flight_reliability, overhead_summary
- !5 tools answer with structured data but don't declare its shape (outputSchema): flight_status, flight_on_date, airport_board, aircraft_info, aircraft_overhead. If those answers change shape, nothing can catch it; with a schema, every answer
- ✓ConnectsConnected in 672 mspass
- ✓Lists its toolsFound 10 toolspass
- ✓No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.pass
- ✓Fast enoughpass
All good
- ✓Connecting took 672 ms
- ✓Listing tools took 126 ms
- ✓Average tool answer: 233 ms
- ✓aircraft_info: Slowest tool: aircraft_info (435 ms)
- ✓No secrets leakedChecked 5 error messages: no secrets or internal detailspass
- –Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)not tested
Test it yourself
Free and open source. Same checks, same score.
npx qamcp-cli https://planetrack.ai/mcpShow this score on GitHub
Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.
[](https://qamcp.dev/s/ai-planetrack-flight-data.html)Score over time
- 10 Nov 202673
One test so far. New tests will show here.
Reviews
Coming soon: reviews from people who use flight-data, signed in with GitHub, one per person. Reviews never change the score.
QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.
Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works