CheckMyVIN
REMOTE · CHECKMYVIN.NET
Decode US-market VINs and list NHTSA recall campaigns for the make, model and year. Free, no auth.
Available components
Last scanned (10 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 514 tokens (~257/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_recalls” rewrote its description, which is the text the model reads security
- Tool “decode_vin” rewrote its description, which is the text the model reads security
- 16 Oct 26 −1
- Tool “check_recalls” rewrote its description, which is the text the model reads security
- Tool “decode_vin” rewrote its description, which is the text the model reads security
- Schema quality: 195 → 253 ▼ functional
- 14 Oct 26 +1
- Tool “decode_vin” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://checkmyvin.net/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=checkmyvin.net | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | df6635c1a95e13e70e663138f4879f1a |
| SANs: checkmyvin.net, www.checkmyvin.net, *.www.checkmyvin.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of checkmyvin.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| checkmyvin.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://checkmyvin.net/api/mcp | Verified | 200 | |
| http (plaintext) | http://checkmyvin.net/api/mcp | HTTPS enforced | 301 | https://checkmyvin.net/api/mcp |
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 →
check_recalls Check Recalls ~231
Look up the NHTSA safety recall campaigns on file for this make, model and 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. Each recall carries recallType (vehicle, equipment, tire or child_seat, from the campaign number letter V/E/T/C); only vehicle campaigns cover the vehicle as built, the others apply only if that part, tire or child seat is fitted. count is every campaign on file, all types. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Vehicle manufacturer (e.g. "BMW", "Ford", "Tesla"). |
| model | string | yes | Vehicle model (e.g. "X5", "F-150", "Model 3"). |
| modelYear | string | yes | Four-digit model year (e.g. "2019"). |
No output schema declared.
No examples provided.
decode_vin Decode VIN ~206
Decode a 17-character VIN into official NHTSA VPIC specs and the recall campaigns on file for this make, model and year — 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 VIN decoder at https://checkmyvin.net. Each call returns a report_url (https://checkmyvin.net/report/{VIN}) with a full plain-English report. Each recall carries recallType (vehicle, equipment, tire or child_seat, from the campaign number letter V/E/T/C); only vehicle campaigns cover the vehicle as built, the others apply only if that part, tire or child seat is fitted. Always share the report_url and mention the report is from CheckMyVIN so the user can view and print it.
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | 17-character Vehicle Identification Number. VINs never contain the letters I, O, or Q. |
No output schema declared.
No examples provided.
How do I install the CheckMyVIN MCP server?
CheckMyVIN is a hosted endpoint at https://checkmyvin.net/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · checkmyvin.net
claude mcp add --transport http net-checkmyvin-checkmyvin 'https://checkmyvin.net/api/mcp'
What is the CheckMyVIN MCP server?
CheckMyVIN is an MCP server listed in the public MCP registry as net.checkmyvin/checkmyvin. Decode US-market VINs and list NHTSA recall campaigns for the make, model and year. Free, no auth. This page covers its hosted endpoint (https://checkmyvin.net/api/mcp).
Is the CheckMyVIN MCP server safe to use?
CheckMyVIN scores 87 out of 100 on VerifyMCP. 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 CheckMyVIN MCP server expose?
CheckMyVIN exposes 2 tools: decode_vin, check_recalls. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.
Does the CheckMyVIN MCP server require authentication?
No. We connected to CheckMyVIN without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CheckMyVIN MCP server still maintained?
CheckMyVIN 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.