CheckMyVIN MCP server
net.checkmyvin/checkmyvincheckmyvin.netstreamable-httpv1.0.1Scanned
Decode US-market VINs and list NHTSA recall campaigns for the make, model and year. Free, no auth.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- 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 CheckMyVIN MCP server can do
The CheckMyVIN MCP server is published by checkmyvin.net, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: decode_vin and check_recalls), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (decode_vin and check_recalls).
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, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.0.1.
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.
2 tools
Changes things 2Claude Code: ask
check_recallsLook up the NHTSA safety recall campaigns on file for this make, model and year.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
decode_vinDecode 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 Unit…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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:16 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
- 2
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://checkmyvin.net/api/mcp: tools/list returned 2 tools to an anonymous client, including decode_vin (write), check_recalls (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.
Tools2 changed.~2 changedView diff
- Changed:check_recallsChanges thingsdescription
- Changed:decode_vinChanges thingsdescription
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http checkmyvin https://checkmyvin.net/api/mcpclaude mcp add --transport http checkmyvin https://checkmyvin.net/api/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": [],
"ask": [
"mcp__checkmyvin__decode_vin",
"mcp__checkmyvin__check_recalls"
],
"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 checkmyvin. Review it before you use it.
Capability tags behind 2 rules
- mcp__checkmyvin__decode_vin untrusted-input
- mcp__checkmyvin__check_recalls untrusted-input
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/net.checkmyvin/checkmyvin/verify?hash=655d766b2d03c91792ee00f98836bdd67c5b7c6ac042aa74f098a972a61e60ba" | jq -e '.changed == false'Pinned hash 655d766b2d03, from Nov 9, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.checkmyvin/checkmyvin/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.checkmyvin/checkmyvin)Source: MCP Registry. Synced Oct 28, 2026, 03:17 UTC.
CheckMyVIN MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CheckMyVIN MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 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 CheckMyVIN MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CheckMyVIN 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 CheckMyVIN MCP server have?
- 2 tools: 2 write. decode_vin and check_recalls.
Does the CheckMyVIN MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CheckMyVIN MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CheckMyVIN MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 28, 2026. Every change is on this page and in its Atom feed.