MCP.Market

Ntsb Investigations MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/ntsb-investigations·v0.2.1

NTSB Investigations — aviation accident/incident investigations by registration (tail) number or…

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Ntsb Investigations yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Ntsb Investigations tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Ntsb Investigations 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
213 ms
faster than 61% of 30,031 servers

Release history: 4 versions in the registry since 2026-10-08, latest 2026-11-03, typically one every 6 days.

Install Ntsb Investigations in Claude Code, Cursor or VS Code

claude mcp add --transport http ntsb-investigations https://gateway.pipeworx.io/ntsb-investigations/mcp
Add to Cursor

What the publisher says

From the Ntsb Investigations repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/ntsb-investigations

NTSB aviation accident/incident investigations, searchable by aircraft registration (tail number) or by make/model. Returns NTSB number, event date, location, injury level, phase/occurrence, probable cause, findings, and the NTSB docket link for each match.

Part of Pipeworx — an MCP gateway connecting AI agents to 1721+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

— requires registration or make. model narrows within a make (matches "172", "172S", "172N", ... by prefix). year filters by event year, and is also how a registration match is narrowed when an N-number has been reassigned to a different aircraft over time (see below). Returns { found, dataasof, source, count, query, results[] }, or { found: false, dataasof, source, query } with no matches.

  • ntsbsearchinvestigations({ registration?, make?, model?, year?, state?, limit? })

Auth

Keyless. No upstream account, no API key.

Data sources

database (avall.zip, a Microsoft Access .mdb bulk file, confirmed live 2026-10-07 at ~96 MB zipped / ~561 MB unzipped). This is the full, current dataset — the SAME data CAROL's aviation search queries, published as the bulk file NTSB itself ships for exactly this use.

  • — the NTSB's own eADMS aviation accident

a given ntsb_number, where the final report and supporting documents are published. Confirmed live (HTTP 200) for a real case pulled from this same dataset.

  • — the NTSB docket page for

Why not CAROL's own search, or the newer developer API

CAROL (data.ntsb.gov/carol-main-public), NTSB's modern search UI, was probed first. Its JSON endpoints (api/Query/Main, api/Query/FileExport) are undocumented, and every QueryGroups/QueryRules request shape reverse-engineered from a public third-party CAROL proxy and from NTSB's own CAROL-Guide.pdf returned HTTP 500 ("An unknown exception occured." / "An error has occurred.") — the frontend ships no devtools-free schema and the server gives no hint why the shape it wants differs from what a real browser session sends (likely a server-side session/anti-forgery requirement CAROL's own JS sets up before the first query).

NTSB also runs a newer REST API at developer.ntsb.gov (Aviation / Safety Recommendations / Data Dictionary APIs, via an Azure API Management gateway). That portal requires signing up for a developer account and a subscription key before any call succeeds — an authentication wall, which per this repo's standing rule is never a free pass to build around without a separate key decision, unlike the plain public bulk file this pack actually reads.

Refreshing the data

node mcps/ntsb-investigations/scripts/refresh.mjs [--local-mdb ] [--dry-run] [--r2-mode auto|api|wrangler] [--shard-max-bytes ]

Downloads avall.zip, unzips it, runs mdb-export (mdbtools — brew install mdbtools / apt install mdbtools) on five tables (aircraft, events, narratives, Findings, EventsSequence, eADMSPUBDataDictionary), joins them into one flat case-per-aircraft list, then shards it into the shared pipeworx-datasets R2 bucket (same bucket as mcps/indiana-code, mcps/illinois-code, mcps/crs-reports — see scripts/lib/statute-store.mjs) rather than writing one object:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Ntsb Investigations: common questions

Is Ntsb Investigations MCP server safe?
Mostly: it is graded B (77/100). Read the Ntsb Investigations safety report
How do I install Ntsb Investigations?
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 Ntsb Investigations need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Ntsb Investigations maintained?
The last commit was 27 days ago (2026-10-08). The latest release is v0.2.1.
Is Ntsb Investigations up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Ntsb Investigations 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 213 ms (faster than 61% of 30,031 servers). Full comparison.

More from pipeworx-io →