CheckMyVIN MCP server

Which servers in the official MCP registry are CheckMyVIN's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-16

← Back to CheckMyVIN

Whose server it is

Registry namenet.checkmyvin/checkmyvinverified in the MCP registry

The registry name sits under checkmyvin.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-16

Stateanswerschecked 2026-10-16
Tools2
Server calls itselfcheckmyvin
Server version1.0.0
Protocol version2025-06-18

On 2026-10-16 the server answered initialize and tools/list without a sign-in. First answer in 323 ms.

Tools it offers2 tools · read 2026-10-16

decode_vin
Decode a 17-character VIN into official NHTSA VPIC specs and every open recall — 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…
check_recalls
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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "checkmyvin": {
      "type": "http",
      "url": "https://checkmyvin.net/api/mcp"
    }
  }
}

OpenAPI spec

2 paths, read 2026-10-16. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.