CheckMyVIN is an MCP server with 2 tools an agent can call, among them check_recalls, decode_vin. It answers at https://checkmyvin.net/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Decode US-market VINs and list NHTSA recall campaigns for the make, model and year. Free, no auth.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 remedy Inputs: make, model, modelYear |
decode_vin | 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 Inputs: vin |
Every block below points at https://checkmyvin.net/api/mcp. Pick your client and copy.
claude mcp add --transport http checkmyvin https://checkmyvin.net/api/mcp
{
"mcpServers": {
"checkmyvin": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://checkmyvin.net/api/mcp"]
}
}
}{
"mcpServers": {
"checkmyvin": {
"url": "https://checkmyvin.net/api/mcp"
}
}
}{
"servers": {
"checkmyvin": {
"type": "http",
"url": "https://checkmyvin.net/api/mcp"
}
}
}{
"context_servers": {
"checkmyvin": {
"url": "https://checkmyvin.net/api/mcp"
}
}
}{
"mcpServers": {
"checkmyvin": {
"serverUrl": "https://checkmyvin.net/api/mcp"
}
}
}{
"mcpServers": {
"checkmyvin": {
"url": "https://checkmyvin.net/api/mcp"
}
}
}name: CheckMyVIN
version: 0.0.1
schema: v1
mcpServers:
- name: CheckMyVIN
type: streamable-http
url: https://checkmyvin.net/api/mcp{
"mcpServers": {
"checkmyvin": {
"httpUrl": "https://checkmyvin.net/api/mcp"
}
}
}{
"mcpServers": {
"checkmyvin": {
"type": "http",
"url": "https://checkmyvin.net/api/mcp"
}
}
}{
"mcpServers": {
"checkmyvin": {
"url": "https://checkmyvin.net/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fcheckmyvin.net%2Fapi%2Fmcp&type=streamable_http&id=checkmyvin&name=CheckMyVIN
It answered our last check on 24 October 2026 in 1131 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by checkmyvin.net and served from checkmyvin.net, the vendor's own domain: https://checkmyvin.net/api/mcp.
2, as returned by the server's own tools/list on 22 September 2026: check_recalls, decode_vin.
It answered our last check on 24 October 2026 in 1131 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://checkmyvin.net/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: net.checkmyvin. Endpoint host: checkmyvin.net. ARD identifier: urn:air:net.checkmyvin:mcp:checkmyvin.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.