VIN Decoder + Safety Recalls (NHTSA) MCP Server

by pcp183 Your server? Claim it

not responding

VIN Decoder + Safety Recalls (NHTSA) is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Decode a VIN and list NHTSA recalls for that model (US data). $0.003/call via x402.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 23 days of history · worst day 0%

23 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

212 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 October 2026. No other catalogue keeps this.

17 Oct a tool description was rewritten vin_decode

17 Oct a tool changed version

VIN Decoder + Safety Recalls (NHTSA) does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add vin-decode --transport http https://vin-decode-production.up.railway.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://vin-decode-production.up.railway.app/mcp

~/.codex/config.toml

[mcp_servers.vin-decode]
url = "https://vin-decode-production.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "vin-decode": {
      "url": "https://vin-decode-production.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "vin-decode": {
      "type": "http",
      "url": "https://vin-decode-production.up.railway.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

vin

vin_decode

Identify a vehicle from its VIN and check for safety recalls before a purchase, listing, insurance quote or repair. Decodes a 17-character VIN with NHTSA vPIC (make, model, year, trim, body, engine, fuel, drive, transmission, plant, check-digit validation) and lists NHTSA recall campaigns for that make, model and year. Recalls are per model, not VIN-specific. Use when a VIN is all you have; coverage is best for US-market vehicles. $0.003 per call, USDC on Base (x402).

Endpoints

URL	Transport	State	Latency	Checked
https://vin-decode-production.up.railway.app/mcp	streamable-http	answering	212 ms	9 min ago

Alternatives to VIN Decoder + Safety Recalls (NHTSA)

same job, measured the same way

Vin Recall MCP

by pratikmehkarkar

Decodes US VINs and looks up open NHTSA safety recall campaigns for a vehicle.

2 tools answering

CheckMyVIN

by checkmyvin

Decode US-market VINs and list NHTSA recall campaigns for the make, model and year. Free, no auth.

2 tools answering

Nhtsa MCP

by mrfentmen

NHTSA: VIN decoding, safety recalls, owner complaints, make and model catalogues — keyless.

147 installs/wk local only

US Vehicle Recalls & VIN Check MCP

by donniertf-hub

Decode any VIN and see NHTSA safety recalls and owner complaints.

3 tools answering

Carstat

by carstat

Vehicle specs, VIN decoding, NHTSA recalls and safety ratings by year, make, model or VIN.

answering

RecallChecker — Vehicle Safety Recalls

by checkrecall

Check U.S. NHTSA vehicle safety recall campaigns by make, model, and year. Live official data.

1 tools answering

UK Data: US vehicle safety (NHTSA)

by co-reliness

US vehicle safety from NHTSA: recalls, owner complaints, crash-test ratings and VIN checks

10 tools answering

NHTSA Vehicle Safety

by olyport

Vehicle safety recalls, complaints, and crash data from NHTSA

6 tools answering

VIN Decoder + Safety Recalls (NHTSA) — questions

Answers built from our own checks of this server.

What can VIN Decoder + Safety Recalls (NHTSA) do?

It exposes 1 tools, read directly from the server on our last check. Among them: vin_decode. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is VIN Decoder + Safety Recalls (NHTSA) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 212 ms. The bar chart above shows every period we have measured.

Is VIN Decoder + Safety Recalls (NHTSA) still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists VIN Decoder + Safety Recalls (NHTSA) as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect VIN Decoder + Safety Recalls (NHTSA)?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does VIN Decoder + Safety Recalls (NHTSA) need an API key?

No. VIN Decoder + Safety Recalls (NHTSA) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.