Ntsb Investigations
NPM · @PIPEWORX/MCP-NTSB-INVESTIGATIONS · 2 COMPONENTS
NTSB Investigations — aviation accident/incident investigations by registration (tail) number or…
Available components
Last scanned (12 hours ago)
Scores higher than 69% of npm servers
Category Health and Science
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-ntsb-investigations). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 853 tokens (~426/item across 2 items; 2 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 Management23
- Stability observed for 7 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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 →
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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-ntsb-investigations@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-ntsb-investigations |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ntsb-investigations/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679478460 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4a47ef473e2b8bc7d60bd272dd59c12b0d407e0703e055f1258754228231a18d760bd9abe6bde907e6ff16da21fa9a4c25ab08a7193d1ef6ac7e9897c |
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 →
ntsb_accidents_by_period ~382
NTSB aviation accidents and incidents — plane crashes — in a date range, across every aircraft make, grouped by US state with counts. Answers questions like "fatal aviation accidents in Alaska in 2025", "plane crashes by state in May 2024", or "how many fatal crashes in California last year" in one call. Filter by `injury_level` (fatal, serious, minor, none) and/or `state`; `from`/`to` accept "YYYY", "YYYY-MM", or "YYYY-MM-DD" and are both inclusive (`to` defaults to the end of `from`'s own year/month). Returns per-state counts (`by_state`) for every match plus up to 200 individual records — NTSB number, event date, location, injury level, phase, probable cause, docket link. Sourced from the NTSB's own eADMS aviation accident database (data.ntsb.gov/avdata); a range spanning more than 8 calendar years is refused — narrow it.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start of the date range, inclusive. "YYYY", "YYYY-MM", or "YYYY-MM-DD", e.g. "2024-05" or "2025-01-01". |
| injury_level | string | – | Highest injury level reported for the event: fatal, serious, minor, or none. |
| limit | integer | – | Max individual records to return (default 50, max 200). `by_state` counts cover every match regardless of this cap. |
| state | string | – | US state postal abbreviation of the event location, e.g. "AK". |
| to | string | – | End of the date range, inclusive, same formats as `from`. Omit to default to the end of `from`'s own year/month. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_state | array | – | – |
| count | integer | – | – |
| data_as_of | string | yes | – |
| found | boolean | yes | – |
| query | object | – | – |
| results | array | – | – |
| source | string | yes | – |
| truncated | boolean | – | – |
No examples provided.
ntsb_search_investigations ~412
NTSB aviation accident/incident investigations — plane crashes — by aircraft registration (tail) number or by make/model, optionally filtered by `state`, `year`, or `injury_level` (fatal, serious, minor, none). Returns NTSB number, event date, location, injury level, phase/occurrence, probable cause, findings, and the NTSB docket link for each match. Registration numbers (N-numbers) are reused over time by different aircraft; pass `year` to narrow a registration match to one incarnation when more than one comes back. A broad make with no `model` or `year` may be asked to narrow — this reads a small sharded dataset, never a full scan. For a date-range or cross-make query with no make/registration (e.g. "fatal accidents in Alaska in 2025"), use `ntsb_accidents_by_period` instead. Sourced from the NTSB's own eADMS aviation accident database (data.ntsb.gov/avdata).
| Name | Type | Req | Description |
|---|---|---|---|
| injury_level | string | – | Highest injury level reported for the event: fatal, serious, minor, or none. |
| limit | integer | – | Max results to return (default 25, max 100). |
| make | string | – | Aircraft manufacturer, e.g. "Cessna", "Piper", "Boeing". |
| model | string | – | Aircraft model, e.g. "172" (matches "172", "172S", "172N", ...). Requires `make`. |
| registration | string | – | Aircraft registration / tail number, e.g. "N512SP" (dashes/spacing ignored). |
| state | string | – | US state postal abbreviation of the event location, e.g. "CA". |
| year | integer | – | Limit to events in this calendar year. Required for a common make (e.g. Cessna, Piper) unless `model` is also given. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| data_as_of | string | yes | – |
| found | boolean | yes | – |
| query | object | – | – |
| results | array | – | – |
| source | string | yes | – |
No examples provided.
How do I install the Ntsb Investigations MCP server?
Ntsb Investigations runs locally as an npm package, launched with npx -y @pipeworx/mcp-ntsb-investigations. 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-ntsb-investigations
claude mcp add pipeworx-io-ntsb-investigations -- npx -y @pipeworx/mcp-ntsb-investigations
What is the Ntsb Investigations MCP server?
Ntsb Investigations is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ntsb-investigations. NTSB Investigations, aviation accident/incident investigations by registration (tail) number or… This page covers its npm package (@pipeworx/mcp-ntsb-investigations).
Is the Ntsb Investigations MCP server safe to use?
Ntsb Investigations scores 81 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 Ntsb Investigations MCP server expose?
Ntsb Investigations exposes 2 tools: ntsb_search_investigations, ntsb_accidents_by_period. Their descriptions and schemas cost roughly 794 tokens of context every time the server is loaded.
Is the Ntsb Investigations MCP server still maintained?
Ntsb Investigations 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 Ntsb Investigations MCP server under?
Ntsb Investigations 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 Ntsb Investigations MCP server?
VerifyMCP ran 16 checks on Ntsb Investigations, 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.