Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Airline Starlink Tracker

REMOTE · AIRLINESTARLINKTRACKER.COM · SCANNED SEP 25

Starlink WiFi status for United, Alaska and Hawaiian flights, with per-airline route odds.

75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1649 tokens (~235/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Airline Starlink Tracker MCP server?

Airline Starlink Tracker is a hosted endpoint at https://airlinestarlinktracker.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · airlinestarlinktracker.com

# add to Claude Code
claude mcp add --transport http com-airlinestarlinktracker-starlink-tracker 'https://airlinestarlinktracker.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-airlinestarlinktracker-starlink-tracker": {
      "url": "https://airlinestarlinktracker.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-airlinestarlinktracker-starlink-tracker": {
      "type": "http",
      "url": "https://airlinestarlinktracker.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-airlinestarlinktracker-starlink-tracker]
url = "https://airlinestarlinktracker.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-airlinestarlinktracker-starlink-tracker": {
      "type": "remote",
      "url": "https://airlinestarlinktracker.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-airlinestarlinktracker-starlink-tracker --url 'https://airlinestarlinktracker.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-airlinestarlinktracker-starlink-tracker:
    url: "https://airlinestarlinktracker.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-airlinestarlinktracker-starlink-tracker": {
      "Transport": "http",
      "Url": "https://airlinestarlinktracker.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-airlinestarlinktracker-starlink-tracker -t streamable-http -u 'https://airlinestarlinktracker.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-airlinestarlinktracker-starlink-tracker": {
      "type": "http",
      "url": "https://airlinestarlinktracker.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 22 Sept 26 73

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://airlinestarlinktracker.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=airlinestarlinktracker.com CN=WE1,O=Google Trust Services,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA256 52630b56b25726a50ea3a8ea62cbbe8e
SANs: airlinestarlinktracker.com, *.airlinestarlinktracker.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of airlinestarlinktracker.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
airlinestarlinktracker.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://airlinestarlinktracker.com/mcp Verified 200
http (plaintext) http://airlinestarlinktracker.com/mcp HTTPS enforced 302 https://airlinestarlinktracker.com/mcp
MCP tools · 7 exposed · ~1,274 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_flight ~265

Use when the user asks "does my flight have Starlink/WiFi?" with a specific tracked-airline flight number and date. Returns FIRM YES if assigned to a verified-Starlink plane, FIRM NO if assigned to a verified non-Starlink plane, or a probability estimate if no assignment exists yet (assignments publish ~2 days out). For dates further out, call predict_flight_starlink directly — check_flight just falls through to the same estimate with extra latency.

NameTypeReqDescription
datestringyesFlight date in YYYY-MM-DD format, matched to the departure airport's local calendar date (UTC fallback for unmapped airports).
destinationstring–Optional 3-letter IATA arrival airport of the traveller's leg (e.g. 'SAN'); with origin, picks one leg of a multi-leg flight number.
flight_numberstringyesFlight number, e.g. 'UA544' or just the digits. Also accepts ICAO airline codes like UAL544; use the marketing flight number (UA5212, not SKW5212).
originstring–Optional 3-letter IATA departure airport of the traveller's leg (e.g. 'DEN'); scopes the answer to that leg of a multi-leg flight number.

No output schema declared.

{"date":"2026-05-15","flight_number":"UA544"}
get_fleet_stats ~74

Use when the user asks "how far along is the Starlink rollout?" or wants overall fleet numbers. Returns tracked airlines Starlink installation counts and percentages across mainline and express fleets, plus a per-aircraft-type breakdown (installed/total per family). Not for per-flight checks — use check_flight for that.

Input schema present but exposes no named parameters.

No output schema declared.

{}
list_starlink_aircraft ~113

Use when the user asks about the planes themselves — "which tail numbers have Starlink?", "which aircraft types are equipped?". Returns tracked airlines tail numbers, aircraft types, operators, and install dates (default 50 most recent; pass limit up to 500). Not for finding flights — use search_starlink_flights for that.

NameTypeReqDescription
fleetstring–Filter to only express (regional) or mainline aircraft.
limitinteger–Maximum number of aircraft to return (default 50).

No output schema declared.

{"fleet":"express","limit":100}
{}
plan_starlink_itinerary ~222

Use when the user asks "what's the best way to fly X to Y with Starlink?". Compares Starlink odds on the route across every tracked airline (nonstop, per-carrier). For multi-stop UA routings, connect to unitedstarlinktracker.com/mcp.

NameTypeReqDescription
datestring–Optional YYYY-MM-DD travel date. When within ~2 days (the aircraft-assignment window), uses confirmed tail assignments for higher accuracy. Beyond that, uses historical prediction only — confirmed as…
destinationstringyesDestination airport IATA code (e.g. 'JAX').
max_resultsinteger–Maximum number of full-coverage itineraries (default 8). Up to 3 partial baselines may be appended.
max_stopsinteger–Maximum number of connection stops (default 2, max 3). 0=direct only, 1=one connection, etc.
originstringyesOrigin airport IATA code (e.g. 'SFO').

No output schema declared.

{"destination":"EWR","origin":"SFO"}
{"date":"2026-05-20","destination":"JAX","max_stops":1,"origin":"ORD"}
predict_flight_starlink ~257

Use when the user asks "will my flight have Starlink?" for a date too far out for a confirmed assignment, or with no date at all. Returns the probability that a tracked-airline flight number gets a Starlink plane, from historical observations. Reliability varies: high-confidence (5+ obs) is the most reliable tier but is not a guarantee; low-confidence (0-1 obs) is just the fleet prior. UA1-2999 (mainline) has materially lower coverage than UA3000-6999 (express) — call get_fleet_stats for the current split rather than assuming a rate.

NameTypeReqDescription
datestring–Optional YYYY-MM-DD. ALWAYS PASS if known — the probability is date-agnostic, but when the result is low (<20%) the tool uses this date to look up the actual route and returns a ready-to-run plan_sta…
flight_numberstringyesFlight number, e.g. 'UA544' or just the digits. Also accepts ICAO airline codes like UAL544; use the marketing flight number (UA5212, not SKW5212).

No output schema declared.

{"date":"2026-06-01","flight_number":"UA544"}
{"flight_number":"UA544"}
predict_route_starlink ~180

Use when the user asks "which flights between X and Y have Starlink?" or "what Starlink flights serve airport X?". Single-route lookup: returns tracked airlines flight numbers on a route (or touching an airport) ranked by Starlink probability. Both origin and destination are required (per-airline route comparison). For trip planning with connections, use plan_starlink_itinerary instead — this tool has no connection logic or coverage-ratio ranking. Empty result = route not served by Starlink planes.

NameTypeReqDescription
destinationstring–Destination airport IATA code (e.g. 'EWR', 'DEN'). Case-insensitive.
limitinteger–Maximum number of flight numbers to return (default 10).
originstring–Origin airport IATA code (e.g. 'SFO', 'ORD'). Case-insensitive.

No output schema declared.

{"destination":"EWR","origin":"SFO"}
{"origin":"ORD"}
search_starlink_flights ~163

Use when the user asks "what Starlink flights leave from X tomorrow?" or wants confirmed near-term departures. Returns CONFIRMED Starlink flights in the next ~2 days — firm schedule, not prediction. Pass at least one of origin or destination (both narrows to a single route). Aircraft assignments aren't published further out, so for later dates use predict_route_starlink or plan_starlink_itinerary instead.

NameTypeReqDescription
destinationstring–Destination airport IATA code (e.g. 'LAX', 'DEN'). Case-insensitive.
limitinteger–Maximum number of flights to return (default 20).
originstring–Origin airport IATA code (e.g. 'SFO', 'ORD'). Case-insensitive.

No output schema declared.

{"origin":"ORD"}
{"destination":"EWR","origin":"SFO"}
Common questions

What is the Airline Starlink Tracker MCP server?

Airline Starlink Tracker is an MCP server listed in the public MCP registry as com.airlinestarlinktracker/starlink-tracker. Starlink WiFi status for United, Alaska and Hawaiian flights, with per-airline route odds. This page covers its hosted endpoint (https://airlinestarlinktracker.com/mcp).

Is the Airline Starlink Tracker MCP server safe to use?

Airline Starlink Tracker scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Airline Starlink Tracker MCP server expose?

Airline Starlink Tracker exposes 7 tools: check_flight, get_fleet_stats, list_starlink_aircraft, predict_flight_starlink, plan_starlink_itinerary, and 2 more. Their descriptions and schemas cost roughly 1,274 tokens of context every time the server is loaded.

Does the Airline Starlink Tracker MCP server require authentication?

No. We connected to Airline Starlink Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Airline Starlink Tracker MCP server still maintained?

Airline Starlink Tracker is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.