
Bts Ontime MCP server
online · 100% uptimebts-ontime -- US airline on-time performance and delay causes (fleet #2953).
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Bts Ontime yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Bts Ontime tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Bts Ontime compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 309 ms
- faster than 47% of 30,031 servers
Release history: 3 versions in the registry since 2026-10-13, latest 2026-10-31, typically one every 17 days.
Install Bts Ontime in Claude Code, Cursor or VS Code
claude mcp add --transport http bts-ontime https://gateway.pipeworx.io/bts-ontime/mcp
What the publisher says
From the Bts Ontime repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/bts-ontime
US domestic airline on-time performance and delay causes: monthly on-time %, average arrival delay, cancellations, diversions, and delay minutes broken down by cause (carrier, weather, air-traffic-control/NAS, security, late aircraft) — by route, by carrier, and by arrival airport. Fleet #2953.
Part of Pipeworx — an MCP gateway connecting AI agents to 1779+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
performance for one origin->destination route, optionally scoped to one carrier. Each month carries flights, completed flights, on-time arrivals and on-time %, average arrival delay, cancellations, diversions, and delay minutes by cause.
- route_ontime(origin, dest, carrier?, months?) — monthly on-time
aggregated across one airline's whole network (or just the flights touching one airport).
- carrier_ontime(carrier, airport?, months?) — the same monthly shape,
delay-cause breakdown by carrier for flights ARRIVING at one airport, optionally scoped to a year and/or month. limit defaults to 50 (max 200); a response with more matching rows than returned carries truncated: true and total_matching rather than silently dropping them.
- btsairportdelays(airport, year?, month?, limit?, offset?) —
delay-cause rows, organized by year first, for scanning a whole year across carriers or airports. Same limit/truncated/totalmatching pagination as btsairport_delays.
- delay_causes(year, carrier?, airport?, limit?, offset?) — the same
Call this first if you're not sure a given period is covered.
- list_coverage() — the earliest/latest month actually loaded, and when.
Carrier accepts either the 2-letter reporting-carrier code ("DL") or a common airline name ("Delta"). Airport codes are validated against what is actually loaded (not a static list) — an unrecognized code is refused with a clear error, never an empty success.
Auth
Keyless. The tools answer only through the Pipeworx gateway, which holds the data; a standalone npm install has no data to read, and every tool throws a clear "not bound in this runtime" error there instead of returning an empty list.
Data sources
Carrier On-Time Performance" monthly bulk data. US federal government work: public domain (17 U.S.C. §105). The agency publishes bulk files only (no live query API for this dataset), so this pack builds a copy (scripts/bts-ontime/load-data.mjs) rather than proxying — raw flight-level rows (~600k/month) are never stored; the loader aggregates each month down to two small tables and discards the raw file before moving to the next one.
- US DOT Bureau of Transportation Statistics (BTS), TranStats — "Reporting
What delay_cause is, and is not
BTS separately publishes its own "Airline Delay Cause" product, which apportions each delayed flight's minutes into fractional per-cause counts via a methodology this pack does not reimplement. The delaycause table here is derived from the same underlying per-flight delay-minute fields (carrier/weather/NAS/security/late-aircraft) as routemonth, rolled up by carrier x arrival-airport x month, and reported as minute sums, not fractional counts. It will be consistent with BTS's own published cause breakdown but is not guaranteed to match it row-for-row — this is one pipeline over one raw source, not a second download of BTS's own aggregate.
Known gaps — read before extending this pack
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Bts Ontime: common questions
- Is Bts Ontime MCP server safe?
- Mostly: it is graded B (77/100). Read the Bts Ontime safety report
- How do I install Bts Ontime?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Bts Ontime need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Bts Ontime maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v0.2.1.
- Is Bts Ontime up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Bts Ontime compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 309 ms (faster than 47% of 30,031 servers). Full comparison.