Ext Ops Panel
Open dashboard
Comparison

Flightaware vs Flightstats

Flightaware is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). Flightstats is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-03. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceFlightawareFlightstats
Official MCP Registry Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Flightaware vs Flightstats
FactFlightawareFlightstats
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release2026-11-022026-11-02
Where it runs (differs)Remote server (gateway.pipeworx.io/flightaware/mcp)Remote server (gateway.pipeworx.io/flightstats/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/pipeworx-io/mcp-flightawaregithub.com/pipeworx-io/mcp-flightstats
Changes in the last 7 days44
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 41 h agoResponded 3 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Flightaware

In its own words, on Official MCP Registry:

FlightAware MCP — wraps FlightAware AeroAPI v4 (aeroapi.flightaware.com)

Flightstats

In its own words, on Official MCP Registry:

FlightStats MCP — wraps the Cirium FlightStats Flex API (api.flightstats.com/flex)

How to run each

Flightaware As a remote MCP server

Claude Code
claude mcp add --transport http flightaware https://gateway.pipeworx.io/flightaware/mcp

Requires: PIPEWORX_API_KEY (secret)

Flightstats As a remote MCP server

Claude Code
claude mcp add --transport http flightstats https://gateway.pipeworx.io/flightstats/mcp

Requires: PIPEWORX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Only Flightaware has

  • flightaware_airport_flights
  • flightaware_flight_position
  • flightaware_flight_status
  • flightaware_flight_track

Only Flightstats has

  • flightstats_airport_status
  • flightstats_flight_status
  • flightstats_schedule

Both have

  • ai_visibility_check
  • archive_compare
  • archive_evidence
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • bet_research
  • classify_row
  • company_facts
  • company_register_search
  • compare_entities
  • deep_research
Show the remaining 32
  • discover_tools
  • entity_profile
  • forget
  • generate_llms_txt
  • kalshi_weather_edge
  • list_subscriptions
  • pipeworx_feedback
  • pipeworx_trending
  • polymarket_arbitrage
  • polymarket_edge_tracker
  • polymarket_edges
  • polymarket_fill_risk
  • polymarket_kalshi_spread
  • prediction_calibration
  • recall
  • recent_alerts
  • recent_changes
  • release_calendar_markets
  • remember
  • research_row
  • resolution_audit
  • resolution_diff
  • resolve_entity
  • scan_competitor_ai_presence
  • scan_dependency
  • search_within
  • subscribe
  • suggest_questions
  • unsubscribe
  • updown_divergence_rate
  • updown_venue_compare
  • validate_claim

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Flightaware as of 2026-11-03; Flightstats as of 2026-11-03). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Flightaware asks for

None

Only Flightstats asks for

None

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Flightaware · What it can do: Flightstats · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built