Skip to content

flight-data MCP server

ai.planetrack/flight-dataplanetrack.aistreamable-httpv1.0.0Scanned

Live flight status, airport boards, aircraft lookups and what is overhead, from PlaneTrack.ai.

10 tools: 9 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 9 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

9 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the flight-data MCP server can do

The flight-data MCP server is published by planetrack.ai, a domain the MCP Registry verified. It has 10 tools. It can create or change data (9 tools: flight_on_date, airport_board, aircraft_info, aircraft_overhead and 5 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 9Claude Code: ask
  • aircraft_infoAn aircraft by registration (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • aircraft_overheadAircraft flying right now within radius_km (max 30) of a latitude/longitude, nearest first: callsign, type, altitude, speed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Aircraft flying right now within radius_km (max 30) of a latitude/longitude, nearest first: callsign, type, altitude, speed. Free, no key.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • aircraft_trackPositions of one aircraft (Mode-S hex, e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Positions of one aircraft (Mode-S hex, e.g. a1b2c3) over the last minutes (5 to 1440). 20 credits.
  • airport_boardLive departures and arrivals board for an airport (ICAO like KJFK or IATA like JFK): flight, other airport, status, time.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Live departures and arrivals board for an airport (ICAO like KJFK or IATA like JFK): flight, other airport, status, time. Free, no key.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • flight_historyPast legs of a flight number/callsign as flown (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Past legs of a flight number/callsign as flown (e.g. UAL1, BAW117): dates, airports, times, aircraft. 20 credits.
  • flight_on_dateWhat 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • flight_reliabilityOn-time performance for a flight number, a route (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • live_aircraft_nearAircraft currently airborne within radius_km of a latitude/longitude, nearest first, with callsign, altitude, heading, speed and type.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Aircraft currently airborne within radius_km of a latitude/longitude, nearest first, with callsign, altitude, heading, speed and type. 10 credits.
  • 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, rarest visitor.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • flight_statusLive status of a flight that is in the air now, by callsign or flight number as broadcast (e.g.No findings

    Why it is in this group

    • The name "flight_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://planetrack.ai/mcp: tools/list returned 10 tools to an anonymous client, including flight_on_date (write), airport_board (write), aircraft_info (write), aircraft_overhead (write), live_aircraft_near (write) and 4 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http flight-data https://planetrack.ai/mcp
claude mcp add --transport http flight-data https://planetrack.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__flight-data__flight_status"
    ],
    "ask": [
      "mcp__flight-data__flight_on_date",
      "mcp__flight-data__airport_board",
      "mcp__flight-data__aircraft_info",
      "mcp__flight-data__aircraft_overhead",
      "mcp__flight-data__live_aircraft_near",
      "mcp__flight-data__aircraft_track",
      "mcp__flight-data__flight_history",
      "mcp__flight-data__flight_reliability",
      "mcp__flight-data__overhead_summary"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as flight-data. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.planetrack/flight-data/verify?hash=3179e8c5663a174fc50fbb942da500cf5220bf16e666cb162279fcccdc079e34" | jq -e '.changed == false'

Pinned hash 3179e8c5663a, from Nov 10, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.planetrack/flight-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.planetrack/flight-data
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.planetrack/flight-data.svg)](https://radar.anlyon.com/servers/ai.planetrack/flight-data)

Source: MCP Registry. Synced Nov 10, 2026, 17:17 UTC.

flight-data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the flight-data MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the flight-data MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the flight-data MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the flight-data MCP server have?

10 tools: 9 write, 1 read. flight_on_date, airport_board, aircraft_info, aircraft_overhead, live_aircraft_near, aircraft_track, flight_history, flight_reliability and 2 more.

Does the flight-data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the flight-data MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the flight-data MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.