# Ntsb Investigations (npm · @pipeworx/mcp-ntsb-investigations)

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

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 85/100, [markdown](https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/ntsb-investigations-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/ntsb-investigations-mcp)
- npm · `@pipeworx/mcp-ntsb-investigations`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/pipeworx-mcp-ntsb-investigations.md), [page](https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/pipeworx-mcp-ntsb-investigations)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ntsb-investigations`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ntsb-investigations).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-ntsb-investigations -- npx -y @pipeworx/mcp-ntsb-investigations
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-ntsb-investigations": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ntsb-investigations"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-ntsb-investigations": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ntsb-investigations"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-ntsb-investigations -- npx -y @pipeworx/mcp-ntsb-investigations
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-ntsb-investigations": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-ntsb-investigations"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ntsb-investigations --command npx --arg -y --arg @pipeworx/mcp-ntsb-investigations
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-ntsb-investigations:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-ntsb-investigations"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-ntsb-investigations": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-ntsb-investigations"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-ntsb-investigations -t stdio -c npx -a -y @pipeworx/mcp-ntsb-investigations
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-ntsb-investigations": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ntsb-investigations"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, +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.

### 2026-11-04 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 65, −13)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 78, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `ntsb_search_investigations` (~412 tokens)

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).

Input parameters:

- `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.

Output parameters:

- `count` (integer)
- `data_as_of` (string)
- `found` (boolean)
- `query` (object)
- `results` (array)
- `source` (string)

### `ntsb_accidents_by_period` (~382 tokens)

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.

Input parameters:

- `from` (string, required): 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.

Output parameters:

- `by_state` (array)
- `count` (integer)
- `data_as_of` (string)
- `found` (boolean)
- `query` (object)
- `results` (array)
- `source` (string)
- `truncated` (boolean)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/pipeworx-mcp-ntsb-investigations#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 65
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-ntsb-investigations
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ntsb-investigations
- Repository: https://github.com/pipeworx-io/mcp-ntsb-investigations
- Website: https://pipeworx.io/packs/ntsb-investigations
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/pipeworx-mcp-ntsb-investigations.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/pipeworx-mcp-ntsb-investigations/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/pipeworx-mcp-ntsb-investigations.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ntsb-investigations/pipeworx-mcp-ntsb-investigations