NHTSA Vehicle Safety MCP server
com.olyport/nhtsaolyport.comstreamable-httpv1.1.0Scanned
Vehicle safety recalls, complaints, and crash data from NHTSA
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the NHTSA Vehicle Safety MCP server can do
The NHTSA Vehicle Safety MCP server is published by olyport.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: decode_vin), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 1Claude Code: ask
decode_vinDecode a Vehicle Identification Number (VIN) to get vehicle details.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Decode a Vehicle Identification Number (VIN) to get vehicle details. Returns make, model, year, body class, engine info, safety features, and other attributes encoded in the 17-character VIN. Args: vin: A 17-character Vehicle Identification Number (e.g. '1HGBH41JXMN109186').
Only reads 5Show 5 read-only tools
complaint_trends_by_componentGet complaint counts by vehicle component for a specific make/model/year.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get complaint counts by vehicle component for a specific make/model/year. Shows which parts of the vehicle consumers report the most problems with (e.g. brakes, engine, electrical system). Useful for identifying systemic vehicle defect patterns. Args: make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford'). model: Vehicle model name (e.g. 'Camry', 'F-150'). year: Model year (e.g. 2023).
get_complaintsGet consumer complaints about vehicles filed with NHTSA.No findings
Why it is in this group
- The name "get_complaints" says "get": a word for reading.
Description, as the server wrote it Get consumer complaints about vehicles filed with NHTSA. Search for safety complaints by make, model, and/or year. Returns complaint descriptions, components involved, and crash/injury data. At least one filter (make, model, or year) should be provided. Args: make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford'). model: Vehicle model name (e.g. 'Camry', 'F-150'). year: Model year (e.g. 2023). limit: Maximum number of complaints to return (default 25).
get_crash_statisticsGet fatal crash statistics from the NHTSA Fatality Analysis Reporting System (FARS).No findings
Why it is in this group
- The name "get_crash_statistics" says "get": a word for reading.
Description, as the server wrote it Get fatal crash statistics from the NHTSA Fatality Analysis Reporting System (FARS). Returns fatal motor vehicle crash data for a state, including total fatalities, fatalities by person type (drivers, passengers, pedestrians), and alcohol-involved crashes. Args: state: Two-digit state FIPS code (e.g. '06' for California, '48' for Texas) or two-letter state abbreviation (e.g. 'CA', 'TX'). year: Year for statistics (e.g. 2022). Defaults to the most recent available year.
get_recallsGet vehicle safety recalls from NHTSA.No findings
Why it is in this group
- The name "get_recalls" says "get": a word for reading.
Description, as the server wrote it Get vehicle safety recalls from NHTSA. Search for recalls by make, model, and/or year. Returns recall campaigns including the defect description, remedy, and affected vehicles. At least one filter (make, model, or year) should be provided. Args: make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford', 'Honda'). model: Vehicle model name (e.g. 'Camry', 'F-150', 'Civic'). year: Model year (e.g. 2023).
local_vehicle_safety_profileGet a vehicle safety profile using national complaint and recall trends.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get a vehicle safety profile using national complaint and recall trends. NHTSA complaints are not geocoded by state, so this returns national-level trends as context for local community safety assessments. Includes the most recent recalls and top complained-about vehicle makes. Args: state: Two-letter state abbreviation (e.g. 'CA', 'TX'). Used for crash statistics; complaint data is national.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.olyport.com/nhtsa/mcp: tools/list returned 6 tools to an anonymous client, including decode_vin (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http nhtsa https://mcp.olyport.com/nhtsa/mcpclaude mcp add --transport http nhtsa https://mcp.olyport.com/nhtsa/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nhtsa__get_recalls",
"mcp__nhtsa__get_complaints",
"mcp__nhtsa__get_crash_statistics",
"mcp__nhtsa__complaint_trends_by_component",
"mcp__nhtsa__local_vehicle_safety_profile"
],
"ask": [
"mcp__nhtsa__decode_vin"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nhtsa. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.olyport/nhtsa/verify?hash=08475c3e298eb8eba2f50a5cb521a8e4afd8e09982a54aec8b23f26c1b1e54c3" | jq -e '.changed == false'Pinned hash 08475c3e298e, from Nov 18, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.olyport/nhtsa/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.olyport/nhtsa)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
NHTSA Vehicle Safety MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NHTSA Vehicle Safety MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the NHTSA Vehicle Safety MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the NHTSA Vehicle Safety MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the NHTSA Vehicle Safety MCP server have?
- 6 tools: 1 write, 5 read. decode_vin, get_recalls, get_complaints, get_crash_statistics, complaint_trends_by_component and local_vehicle_safety_profile.
Does the NHTSA Vehicle Safety MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NHTSA Vehicle Safety MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NHTSA Vehicle Safety MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.