MCP.Market

Vin Recall MCP server

online · 100% uptime
by pratikmehkarkar·io.github.pratikmehkarkar/vin-recall-mcp·v1.0.0
No reviews yet

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

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Vin Recall yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vin Recall tools (2)

write = sends, deletes, buys or posts
  • check_recallsFree

    List open safety recall campaigns for a vehicle by VIN, using the NHTSA Recalls database. Decodes the VIN internally to get make/model/year, then looks up campaigns for that vehicle configuration. Important: results are recall campaigns issued for the make/model/year configuration — this does NOT confirm whether this specific VIN's vehicle was actually repaired at a dealer. Always describe results as 'open recall campaigns for this vehicle,' never as whether the car 'is' or 'isn't' fixed.

  • decode_vinFree

    Decode a 17-character US vehicle VIN into make, model, year, body class, engine cylinders, fuel type, drive type, and assembly plant country, using the NHTSA vPIC database. Covers US-market vehicles built from 1981 onward (the 17-character VIN standard); pre-1981 and some foreign-market vehicles may return partial or no data. Decoded fields are manufacturer-submitted and individual fields may be missing even for a successfully decoded VIN.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 593ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 60 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vin Recall compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
455 ms
faster than 32% of 30,031 servers

What its tools let an agent do: 2 read

Install Vin Recall in Claude Code, Cursor or VS Code

claude mcp add --transport http vin-recall-mcp https://vin-recall-mcp.zenithserver.duckdns.org/mcp
Add to Cursor

What the publisher says

From the Vin Recall repository's README, as published. We do not edit it. Read it on GitHub

vin-recall-mcp

▶️ Watch a 2-minute demo

A remote MCP server that gives any MCP client (Claude, or any other MCP-compatible agent) two tools for free U.S. government vehicle data: decode a VIN and check open safety recalls, both backed by NHTSA's public APIs.

What it does

vin-recall-mcp exposes two tools over a single Streamable HTTP endpoint: decodevin, which turns a 17-character VIN into make, model, year, body class, engine, fuel type, and assembly plant using NHTSA's vPIC database; and checkrecalls, which decodes that same VIN internally and returns every open safety recall campaign NHTSA has on file for that vehicle configuration. Point an MCP client at the URL below and ask it a plain-English question — no API key, no signup, no auth.

Why it exists

NHTSA's vPIC and Recalls APIs are free and genuinely useful, but they're not built for a conversation. decodevin alone returns 100+ key/value pairs per VIN, most of them empty or the literal string "Not Applicable". The recalls endpoint returns HTTP 400 for a legitimate zero-results case, the exact same status it uses for a bad request. Response times swing from a quarter-second to several seconds on the same VIN. None of that is something you want an agent — or a human — parsing raw. This server does the flattening, validation, timeout handling, and error translation once, so an MCP client can just ask "what's this VIN, and does it have any open recalls?" and get a clean answer back.

Architecture

MCP client (Claude, mcp-remote, MCP Inspector, ...)
        │  Streamable HTTP, JSON-RPC
        ▼
Node/Express server  ──▶  NHTSA vPIC API        (decode_vin)
(this repo, self-hosted   NHTSA Recalls API     (check_recalls)
 on Ubuntu behind Caddy)
        │
        ▼
Cleaned, structured response
(flattened fields, human summary, error/caveat notes)

The server is a stateless Node/Express process using @modelcontextprotocol/sdk's StreamableHTTPServerTransport — a fresh McpServer per request, no sessions, no database, no auth layer. It's self-hosted on-prem (Ubuntu Server, "Zenith") behind a Caddy reverse proxy for HTTPS termination, rather than a serverless platform, so the tools run under a real long-lived process with straightforward logs and no cold starts. Tool logic (src/tools.ts) is fully decoupled from the transport (src/server.ts), so it can be — and is — imported and tested directly by the eval suite without a running server.

Tools

decode_vin

Decode a 17-character US VIN into vehicle attributes.

check_recalls

List open NHTSA safety recall campaigns for a vehicle, by VIN.

Install

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vin Recall: common questions

Is Vin Recall MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Vin Recall safety report
How do I install Vin Recall?
It runs remotely at vin-recall-mcp.zenithserver.duckdns.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Vin Recall need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Vin Recall maintained?
The last commit was 101 days ago (2026-07-26). The latest release is v1.0.0.
Is Vin Recall up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Vin Recall compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.