A
licenseNot graded
qualityC
maintenanceEnables querying U.S. vehicle safety and specification data, including VIN decoding, recalls, complaints, investigations, and crash test ratings.
3
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
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
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.
Check U.S. NHTSA vehicle safety recall campaigns by make, model, and year. Live official data.
Vehicle safety recalls, complaints, and crash data from NHTSA
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.18MIT
- AlicenseNot gradedqualityDmaintenanceEnables instant U.S. vehicle recall lookup by make, model, and year using official NHTSA data.MIT
- AlicenseAqualityBmaintenanceDecode 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
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
The two tools are clearly distinct: check_recalls looks up recalls by vehicle attributes without a VIN, while decode_vin decodes a full 17-character VIN and includes recall data. There is no overlap in their primary use cases.
Naming Consistency5/5
Both tool names follow the same verb_noun pattern: check_recalls and decode_vin. The naming is clear, predictable, and consistent.
Tool Count4/5
With only two tools, the server is minimal but focused. It covers the core functionality of recall lookup and VIN decoding. While more tools could be added (e.g., theft check), the count is reasonable for the scope.
Completeness4/5
The tools cover the primary use cases: recalls by vehicle info and full VIN decoding including recalls. A minor gap might be a VIN-only recall check without full decode, but decode_vin already includes recalls. The surface is largely complete for the stated purpose.