NHTSA Vehicle Safety
Server Details
Vehicle safety recalls, complaints, and crash data from NHTSA
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 6 of 6 tools scored.
Every tool has a clearly distinct purpose with no ambiguity. complaint_trends_by_component analyzes component-level trends, decode_vin decodes VINs, get_complaints retrieves complaint details, get_crash_statistics provides fatal crash data, get_recalls fetches recall information, and local_vehicle_safety_profile combines national trends with local crash data. The boundaries between tools are well-defined, preventing misselection.
The naming follows a consistent verb_noun pattern with minor deviations. Most tools use get_ or decode_ prefixes (get_complaints, get_recalls, decode_vin), but complaint_trends_by_component and local_vehicle_safety_profile deviate slightly by using descriptive phrases instead of simple verbs. However, all names are snake_case and clearly describe their functions, maintaining readability.
With 6 tools, the count is well-scoped for the NHTSA vehicle safety domain. Each tool earns its place by covering distinct aspects: VIN decoding, complaint retrieval, recall searches, crash statistics, trend analysis, and safety profiling. This provides comprehensive coverage without being overwhelming or too sparse.
The tool surface provides complete coverage for the NHTSA vehicle safety domain. It includes data retrieval (complaints, recalls, crash stats), analysis (trends, safety profiles), and utility functions (VIN decoding). There are no obvious gaps—agents can perform typical workflows like assessing vehicle safety, investigating defects, or analyzing crash data without dead ends.
Available Tools
6 toolscomplaint_trends_by_componentInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| make | Yes | ||
| year | Yes | ||
| model | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
decode_vinInspect
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').
| Name | Required | Description | Default |
|---|---|---|---|
| vin | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_complaintsInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| make | No | ||
| year | No | ||
| limit | No | ||
| model | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_crash_statisticsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| state | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_recallsInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| make | No | ||
| year | No | ||
| model | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
local_vehicle_safety_profileInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!