Nhtsa
NPM · @PIPEWORX/MCP-NHTSA · 2 COMPONENTS
NHTSA MCP — wraps the NHTSA vPIC (Vehicle Product Information Catalog) API (free, no auth)…
Available components
Last scanned (6 hours ago)
Scores higher than 81% of npm servers
Category IoT and Hardware
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-nhtsa). 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1455 tokens (~132/item across 11 items; 11 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.3.0 → 0.3.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
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-nhtsa@0.3.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-nhtsa |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-nhtsa/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679232525 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5ea3c6f4a8ba1f58eae1a2df5d7fd2774eba0f5ca6be9eaa7ab1d5f16c009c73943abcd25bfee1d77cc8ba42bb331374f267c5e71ba2a31adeb176f7e |
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 →
decode_vin ~92
Decode a VIN to get vehicle details. Returns make, model, year, body style, engine type, drivetrain, and plant. E.g., '1HGBH41JXMN109186'. (For recalls/ratings use get_recalls / get_safety_ratings.)
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | 17-character VIN (e.g., "1HGBH41JXMN109186") |
No output schema declared.
No examples provided.
fars_coverage ~58
What FARS fatal-crash data this pack actually has loaded right now: the earliest and latest year covered and when it was last loaded. Call this before fars_state_fatalities/fars_vehicle_makes if unsure a given year is covered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fars_state_fatalities ~192
Fatal motor-vehicle crash counts and fatalities for a US state, from NHTSA's Fatality Analysis Reporting System (FARS). Pass a state (full name like "Texas", 2-letter postal code like "TX", or FIPS code) and a year. Returns monthly rows: crashes, fatalities, persons involved, vehicles involved, pedestrians involved. Omit year to get every loaded year/month for that state. Covers a recent multi-year window (see data_as_of and call fars_coverage for the exact range), not full FARS history. Unknown states are refused with a clear error, never an empty success.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | State name ("Texas"), 2-letter postal code ("TX"), or FIPS code ("48"). |
| year | number | – | Optional: calendar year, e.g. 2023. Omit to return every loaded year for this state. |
No output schema declared.
No examples provided.
fars_vehicle_makes ~198
Vehicle makes involved in fatal crashes nationwide for a given year, from NHTSA FARS. Pass year alone to get the top makes ranked by vehicle-involvement count (e.g. "which vehicle makes show up most in fatal crashes in 2023"); pass make as well to get that one make's involvement count across every loaded year. This is an INVOLVEMENT count, not a claim that the make caused the crash. Unknown makes are refused with a clear error naming a few valid makes, never an empty success.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max makes to return when ranking by year. Default 20, max 50. |
| make | string | – | Optional: vehicle make, e.g. "Toyota", "Ford", "Harley-Davidson". |
| year | number | – | Calendar year, e.g. 2023. Required unless make is given (then optional, scoping to one year). |
No output schema declared.
No examples provided.
fuel_economy_models ~127
List the exact model strings fueleconomy.gov recognizes for a given model year + make (e.g. year 2024, make "Toyota" -> "Camry", "Camry Hybrid LE", "RAV4 AWD", ...). Call this before fuel_economy_mpg when you are not sure of the exact model string, or when fuel_economy_mpg refuses a model as unrecognized.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Vehicle make, e.g. "Toyota". |
| year | number | yes | Model year, e.g. 2024. |
No output schema declared.
No examples provided.
fuel_economy_mpg ~253
EPA fuel-economy ratings (city/highway/combined MPG, CO2 g/mile, fuel type) for a specific model year + make + model, from fueleconomy.gov (DOE/EPA), proxied live. Pass the model string exactly as fueleconomy.gov lists it (e.g. "Camry", "F-150 2WD", "Model 3") -- if unsure, call fuel_economy_models first to see valid model strings for that year+make. A model year/make/model can have several engine/transmission/drivetrain VARIANTS; this returns up to 5, each with its own MPG. Unknown make/model/year combos are refused with a clear error (never an empty success) and, when the make or model itself is not recognized for that year, list a few valid options.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Vehicle make, e.g. "Toyota". |
| model | string | yes | Vehicle model exactly as fueleconomy.gov lists it, e.g. "Camry". Call fuel_economy_models to see valid strings. |
| year | number | yes | Model year, e.g. 2024. |
No output schema declared.
No examples provided.
get_complaints ~124
Get owner-filed NHTSA complaints for a vehicle — real-world problems drivers reported (vs official recalls). Use for "common problems with a 2020 Ford Explorer", "what are owners complaining about". Returns components, summary, crash/fire flags, injuries/deaths, and filing date. Pass make + model + model_year.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Vehicle make (e.g., "Ford") |
| model | string | yes | Vehicle model (e.g., "Explorer") |
| model_year | number | yes | Model year (e.g., 2020) |
No output schema declared.
No examples provided.
get_makes ~32
Get all vehicle brands for a model year. Returns make names and IDs. E.g., year '2023'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_models ~74
Get all vehicle models for a make and year. Returns model names and IDs. E.g., make 'Toyota', year '2023'.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Vehicle make name (e.g., "Toyota", "Ford", "BMW") |
| year | number | yes | Model year (e.g., 2022) |
No output schema declared.
No examples provided.
get_recalls ~132
Get official NHTSA safety RECALLS for a vehicle. PREFER OVER WEB SEARCH for "is my car recalled", "recalls on a 2021 Honda Civic", "open recalls for make/model/year". Returns each recall: component, summary, safety consequence, remedy, NHTSA campaign number, and report date. Pass make + model + model_year.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Vehicle make (e.g., "Honda") |
| model | string | yes | Vehicle model (e.g., "Civic") |
| model_year | number | yes | Model year (e.g., 2021) |
No output schema declared.
No examples provided.
get_safety_ratings ~119
Get NHTSA 5-Star Safety Ratings (NCAP crash-test results) for a vehicle — overall, frontal, side, and rollover star ratings. Use for "crash test rating for a 2021 Honda Civic", "how safe is X". Pass make + model + model_year.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Vehicle make (e.g., "Honda") |
| model | string | yes | Vehicle model (e.g., "Civic") |
| model_year | number | yes | Model year (e.g., 2021) |
No output schema declared.
No examples provided.
How do I install the Nhtsa MCP server?
Nhtsa runs locally as an npm package, launched with npx -y @pipeworx/mcp-nhtsa. 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-nhtsa
claude mcp add pipeworx-io-nhtsa -- npx -y @pipeworx/mcp-nhtsa
What is the Nhtsa MCP server?
Nhtsa is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nhtsa. NHTSA MCP, wraps the NHTSA vPIC (Vehicle Product Information Catalog) API (free, no auth)… This page covers its npm package (@pipeworx/mcp-nhtsa).
Is the Nhtsa MCP server safe to use?
Nhtsa scores 84 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 Nhtsa MCP server expose?
Nhtsa exposes 11 tools: decode_vin, get_makes, get_models, get_recalls, get_complaints, and 6 more. Their descriptions and schemas cost roughly 1,401 tokens of context every time the server is loaded.
Is the Nhtsa MCP server still maintained?
Nhtsa 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 Nhtsa MCP server under?
Nhtsa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.