Bts Ontime
NPM · @PIPEWORX/MCP-BTS-ONTIME · 2 COMPONENTS
bts-ontime -- US airline on-time performance and delay causes (fleet #2953).
Available components
Last scanned (4 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
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-bts-ontime). 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1134 tokens (~226/item across 5 items; 5 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 Management20
- Stability observed for 6 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-bts-ontime@0.2.1
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-bts-ontime |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-bts-ontime/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606604197 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6bca42b85d4882a782fd80b056bf3cd5e6e750e757af8e12fca4226ed1b4f744f87e800e9d633c3b5c4df694789cd94e9dedb6376d5f4d8f302335060 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bts_airport_delays ~261
Delay-cause breakdown at one US airport (as the ARRIVAL airport), by carrier, from BTS TranStats on-time data: arriving flights, how many arrived 15+ minutes late, cancellations, diversions, and delay minutes attributed to carrier, weather, NAS (air-traffic-control/system), security, and late-aircraft causes. Pass year and/or month to scope to a specific period; omit both to get every loaded month, most recent first. Rows beyond `limit` are reported via truncated/total_matching rather than silently dropped -- narrow with year/month or page with limit/offset to see the rest. Unknown airport codes are refused with a clear error, never an empty success.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | Airport code, e.g. "ORD". |
| limit | number | – | Max rows to return, 1-200. Default 50. A truncated response carries truncated:true and total_matching. |
| month | number | – | Optional: scope to one month (1-12). Requires year to be meaningful alongside it, but works alone too (matches that month in any loaded year). |
| offset | number | – | Pagination offset. Default 0. |
| year | number | – | Optional: scope to one calendar year. |
No output schema declared.
No examples provided.
carrier_ontime ~205
Monthly on-time performance for one airline, aggregated across all its routes (or just the routes touching one airport), from BTS TranStats Reporting Carrier On-Time Performance. Pass carrier as a 2-letter code ("WN") or common name ("Southwest"). Pass airport to scope to flights where that airport is the origin or destination. Returns the same per-month shape as route_ontime (flights, on-time %, average arrival delay, cancellations, diversions, delay minutes by cause). months caps how many of the most recently loaded months to return (default 12). Unknown carrier codes are refused with a clear error, never an empty success.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | – | Optional: scope to flights where this airport is the origin or destination. |
| carrier | string | yes | 2-letter carrier code ("WN") or common name ("Southwest"). |
| months | number | – | How many of the most recently loaded months to return, most recent first. Default 12. |
No output schema declared.
No examples provided.
delay_causes ~260
Delay-cause rows for a given year, optionally scoped to one carrier and/or one (arrival) airport, from BTS TranStats on-time data. Same fields as bts_airport_delays (arriving flights, 15+ minute-late arrivals, cancellations, diversions, delay minutes by cause) but organized by year first rather than by airport first -- use this to scan a whole year across carriers/airports, or to compare one carrier's delay profile across the airports it serves. Rows beyond `limit` are reported via truncated/total_matching rather than silently dropped -- narrow with carrier/airport or page with limit/offset to see the rest. Unknown carrier or airport codes are refused with a clear error, never an empty success.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | – | Optional: arrival-airport code, e.g. "DFW". |
| carrier | string | – | Optional: 2-letter carrier code ("AA") or common name ("American"). |
| limit | number | – | Max rows to return, 1-200. Default 50. A truncated response carries truncated:true and total_matching. |
| offset | number | – | Pagination offset. Default 0. |
| year | number | yes | Calendar year, e.g. 2026. |
No output schema declared.
No examples provided.
list_coverage ~72
What this pack actually has loaded right now: the earliest and latest BTS month covered, how many months, and when it was last loaded. Call this before route_ontime/carrier_ontime/bts_airport_delays/delay_causes if you are not sure a given month or year is covered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
route_ontime ~278
Monthly on-time performance for one US domestic flight route (origin airport -> destination airport), from BTS TranStats Reporting Carrier On-Time Performance. Returns, per month (and per carrier if more than one serves the route): flights, completed flights, on-time arrivals and on-time %, average arrival delay in minutes, cancellations, diversions, and delay minutes broken down by cause (carrier, weather, NAS/air-traffic-control, security, late aircraft). Pass carrier (2-letter code like "DL", or a common name like "Delta") to scope to one airline; omit it to see every carrier that flew the route. months caps how many of the most recently loaded months to return (default 12). Covers the most recent months loaded (see data_as_of and the earliest/latest fields), not full history. Unknown origin/destination airport codes are refused with a clear error, never an empty success.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | – | Optional: 2-letter carrier code ("DL") or common name ("Delta") to scope to one airline. |
| dest | string | yes | Destination airport code, e.g. "LAX". |
| months | number | – | How many of the most recently loaded months to return, most recent first. Default 12. |
| origin | string | yes | Origin airport code, e.g. "JFK". |
No output schema declared.
No examples provided.
How do I install the Bts Ontime MCP server?
Bts Ontime runs locally as an npm package, launched with npx -y @pipeworx/mcp-bts-ontime. 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-bts-ontime
claude mcp add pipeworx-io-bts-ontime -- npx -y @pipeworx/mcp-bts-ontime
What is the Bts Ontime MCP server?
Bts Ontime is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bts-ontime. bts-ontime -- US airline on-time performance and delay causes (fleet #2953). This page covers its npm package (@pipeworx/mcp-bts-ontime).
Is the Bts Ontime MCP server safe to use?
Bts Ontime scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Bts Ontime MCP server expose?
Bts Ontime exposes 5 tools: route_ontime, carrier_ontime, bts_airport_delays, delay_causes, list_coverage. Their descriptions and schemas cost roughly 1,076 tokens of context every time the server is loaded.
Is the Bts Ontime MCP server still maintained?
Bts Ontime is still listed as active in the MCP registry. We last reached this channel on 5 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 Bts Ontime MCP server under?
Bts Ontime declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.