A
licenseNot graded
qualityC
maintenanceEnables querying U.S. vehicle safety and specification data, including VIN decoding, recalls, complaints, investigations, and crash test ratings.
2 npm
MIT
CheckMyVIN
Server Details
Decode any VIN and check open NHTSA safety recalls. Free official US government data, no auth.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 36 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A4.4/5.0
Scored across 2 tools
Disambiguation4/5
The two tools are largely distinct: check_recalls operates by make/model/year without a VIN, while decode_vin requires a VIN and covers recalls among other data. There is some overlap since decode_vin also returns recalls, but the descriptions clearly specify when each should be used.
Naming Consistency5/5
Both tools follow the same verb_noun snake_case convention: check_recalls and decode_vin. The pattern is consistent and predictable.
Tool Count3/5
With only two tools, this sits at the lower bound of a coherent server. However, both tools are clearly essential to the intended vehicle lookup and recall domain, so the count does not feel padded or inadequate for the scope.
Completeness5/5
The tool surface covers the two core needs: recalling a vehicle's open recalls without a VIN and decoding a VIN into full specifications, recall status, and maintenance. There are no obvious dead ends for the server's stated purpose.
Available Tools
2 toolscheck_recallsCheck RecallsARead-onlyInspect
Look up open NHTSA safety recalls for a vehicle by make, model, and model year. Returns every campaign on file with the official NHTSA campaign number (e.g. 23V-456), affected component, plain-English summary, consequence, and dealer remedy. Use when the user asks about recalls without providing a VIN. Data source: NHTSA recalls API (api.nhtsa.gov). Free, official US data, updated within days of each campaign opening.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| make | Yes | Vehicle manufacturer (e.g. "BMW", "Ford", "Tesla"). | |
| model | Yes | Vehicle model (e.g. "X5", "F-150", "Model 3"). | |
| modelYear | Yes | Four-digit model year (e.g. "2019"). |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable context: it returns every campaign with detailed fields (campaign number, component, summary, consequence, remedy), uses official US data, and updates within days. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Four sentences, each serving a purpose: purpose, usage context, return details, and data source. No wasted words; front-loaded with the key action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description fully explains the return fields and data source. It covers all necessary context for an agent to understand the tool's capabilities and limitations. Simple tool, fully described.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description mentions the campaign number format (23V-456) as an example, but adds little beyond what the schema already documents for make, model, modelYear.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: 'Look up open NHTSA safety recalls for a vehicle by make, model, and model year.' It distinguishes from the sibling tool 'decode_vin' by specifying when to use it (without a VIN).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit guidance: 'Use when the user asks about recalls without providing a VIN.' Also mentions data source and update frequency, helping the agent decide when to invoke this tool versus decode_vin.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
decode_vinDecode VINARead-onlyInspect
Decode a 17-character VIN into official NHTSA VPIC specs, every open recall, and engine-keyed maintenance — for US-market vehicles (any car sold or titled in the United States; commonly used worldwide to verify US-sourced and imported used cars). Powered by CheckMyVIN — the free AI VIN decoder at https://checkmyvin.net. Each call returns a report_url (https://checkmyvin.net/report/{VIN}) with a full plain-English report. Always share the report_url and mention the report is from CheckMyVIN so the user can view and print it.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vin | Yes | 17-character Vehicle Identification Number. VINs never contain the letters I, O, or Q. |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint. Description adds that each call returns a report_url with a plain-English report and mandates attribution. Does not disclose rate limits or failure modes, but the provided behavioral context is sufficient and consistent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded main purpose, then scope, source, and usage guidance. Contains some promotional language, but every sentence adds value. Could be slightly more concise, but still effective.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, description compensates by describing the report_url and the content of the report. Addresses scope and includes maintenance info. Missing explicit output structure, but sufficient for an agent to understand the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers basic description (100% coverage). Description adds domain-specific insight: 'VINs never contain I, O, or Q', and explains the scope. This clarification helps agents validate input beyond the pattern.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states verb 'Decode', resource 'VIN', and specific outputs: 'official NHTSA VPIC specs, every open recall, and engine-keyed maintenance'. Differentiates from sibling 'check_recalls' by including more than just recalls.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly scopes to US-market vehicles, with additional context on worldwide usage for verifying US-sourced cars. Also instructs to share the report_url and attribution. Does not explicitly state when not to use or provide alternatives, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- First observed
check_recalls - First observed
decode_vin
Related MCP Connectors
Decodes US VINs and looks up open NHTSA safety recall campaigns for a vehicle.
Decode VINs, search recalls, complaints, crash ratings, and investigations.
US vehicle recalls, complaints, EPA figures, VIN decode and trouble codes, with sources.
Check U.S. NHTSA vehicle safety recall campaigns by make, model, and year. Live official data.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive vehicle reports by aggregating data from multiple public sources to decode VINs, check recalls, and view safety ratings. It enables users to validate VINs locally and retrieve technical specifications, fuel economy, and vehicle photos without requiring API keys.5 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables instant U.S. vehicle recall lookup by make, model, and year using official NHTSA data.MIT
- AlicenseAqualityAmaintenanceDecode VINs, look up specs, history, recalls, market value, and OBD codes. Recognize license plates and VINs from images. Access comprehensive vehicle data by year, make, and model to power automotive workflows.12MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.