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.

FlightStats (Unofficial)

NPM · @PIPEWORX/MCP-FLIGHTSTATS · 2 COMPONENTS

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

+3 this week 90 Trust /100

Last scanned (10 hours ago)

Scores higher than 85% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-flightstats). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 729 tokens (~243/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 0
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.57 → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.1 → 0.2.2 functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-flightstats@0.2.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-flightstats
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-flightstats/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3934197858
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:3477016a9ffa5f7b5929409174181fc25c1c38b0d2d8ba3c30df29618a4c05d9f6ebff9241fe23f6317ace79dc1c3a38de86fef1759c9df2826484c30

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~677 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
flightstats_airport_status ~238

Departures/arrivals at an airport — a live board of flights leaving from or arriving at an airport on a given date/hour. Example: flightstats_airport_status({ airport: "JFK", type: "dep", year: 2026, month: 7, day: 2, hour: 14, _apiKey: "appId:appKey" })

NameTypeReqDescription
_apiKeystringyesFlightStats/Cirium credentials as "appId:appKey" (developer.cirium.com; free eval = 20,000 lifetime calls)
airportstringyesAirport IATA code, e.g. "JFK", "LHR", "SFO"
dayintegeryesDay of month 1-31
hourinteger–Local hour 0-23 (optional, default 0)
monthintegeryesMonth 1-12
typestring–Board type: "dep" for departures (default), "arr" for arrivals
yearintegeryesYear, e.g. 2026

No output schema declared.

No examples provided.

flightstats_flight_status ~230

Status of flight AA100 on a date — gate, delay, baggage. Returns operational status (scheduled vs estimated departure/arrival, gate, terminal, baggage claim) for one specific flight identified by carrier IATA code + flight number + date. Example: flightstats_flight_status({ carrier: "AA", flight: "100", year: 2026, month: 7, day: 2, _apiKey: "appId:appKey" })

NameTypeReqDescription
_apiKeystringyesFlightStats/Cirium credentials as "appId:appKey" (developer.cirium.com; free eval = 20,000 lifetime calls)
carrierstringyesAirline IATA code, e.g. "AA", "DL", "BA"
dayintegeryesDeparture day of month 1-31
flightstringyesFlight number (digits only), e.g. "100"
monthintegeryesDeparture month 1-12
yearintegeryesDeparture year, e.g. 2026

No output schema declared.

No examples provided.

flightstats_schedule ~209

Scheduled flight timetable — the published schedule (departure/arrival airports and times) for a carrier + flight number departing on a date, regardless of live operational status. Example: flightstats_schedule({ carrier: "AA", flight: "100", year: 2026, month: 7, day: 2, _apiKey: "appId:appKey" })

NameTypeReqDescription
_apiKeystringyesFlightStats/Cirium credentials as "appId:appKey" (developer.cirium.com; free eval = 20,000 lifetime calls)
carrierstringyesAirline IATA code, e.g. "AA", "DL", "BA"
dayintegeryesDeparture day of month 1-31
flightstringyesFlight number (digits only), e.g. "100"
monthintegeryesDeparture month 1-12
yearintegeryesDeparture year, e.g. 2026

No output schema declared.

No examples provided.

Install

How do I install the FlightStats (Unofficial) MCP server?

FlightStats (Unofficial) runs locally as an npm package, launched with npx -y @pipeworx/mcp-flightstats. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-flightstats

# add to Claude Code
claude mcp add pipeworx-io-flightstats -- npx -y @pipeworx/mcp-flightstats
Common questions

What is the FlightStats (Unofficial) MCP server?

FlightStats (Unofficial) is an MCP server listed in the public MCP registry as io.github.pipeworx-io/flightstats. Unofficial FlightStats MCP, wraps the Cirium FlightStats Flex API (api.flightstats.com/flex). This page covers its npm package (@pipeworx/mcp-flightstats).

Is the FlightStats (Unofficial) MCP server safe to use?

FlightStats (Unofficial) scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 FlightStats (Unofficial) MCP server expose?

FlightStats (Unofficial) exposes 3 tools: flightstats_flight_status, flightstats_airport_status, flightstats_schedule. Their descriptions and schemas cost roughly 677 tokens of context every time the server is loaded.

Is the FlightStats (Unofficial) MCP server still maintained?

FlightStats (Unofficial) is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the FlightStats (Unofficial) MCP server under?

FlightStats (Unofficial) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the FlightStats (Unofficial) MCP server?

VerifyMCP ran 16 checks on FlightStats (Unofficial), covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.