Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VIN MCP

REMOTE · MCP.VIN

Free VIN decoder: NHTSA specs, recalls, complaints, safety ratings, EPA fuel economy. No API key.

Available components

66 Trust /100

Last scanned (15 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1357 tokens (~61/item across 22 items; 22 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • Tool “decode_vin” rewrote its description, which is the text the model reads security
    • Tool “vin_recall_status” rewrote its description, which is the text the model reads security
    • Schema quality: 53 → 61 ▼ functional
    • “decode_vin” added an optional parameter “transmission” cosmetic
  • 17 Nov 26 0
    • Tool “vin_recall_status” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.vin/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.vin CN=YE2,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 5c78df360b8e6ef7723bc558aadc99d667b
SANs: mcp.vin, www.mcp.vin
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.vin. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
vin. DS published 49082 8 Verified
mcp.vin. DS published 38528 13 Verified
mcp.vin. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https://cdn.imagin.studio; connect-src 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.vin/mcp Verified 200
http (plaintext) http://mcp.vin/mcp HTTPS enforced 301 https://mcp.vin/mcp
MCP tools · 22 exposed · ~1,292 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
auto_loan_benchmarks ~29

Dated Federal Reserve new-car loan benchmark snapshot, not personalized or live loan rates.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

batch_decode ~37

Decode multiple VINs at once (up to 50).

NameTypeReqDescription
vinsarrayyesArray of VINs to decode (max 50)

No output schema declared.

No examples provided.

compare_vehicles ~36

Compare 2–4 distinct VINs without treating missing data as zero or counts as safety rankings.

NameTypeReqDescription
vinsarrayyes–

No output schema declared.

No examples provided.

decode_vin ~204

Decode a VIN and return a vehicle report: specs, recalls (with manufacturer build-date ranges), a complaint summary with the most recent complaints, safety ratings, fuel economy, EPA test-vehicle data, parts content and origin (MY2020+), historical production and theft (MY1998-2012), and photo URLs. decode_checks checks the official decode field by field (drive, engine, electrification, transmission, speeds, seats, GVWR) against the manufacturer's description of this VIN, NHTSA test vehicles with the same VIN pattern and EPA's configurations: confirmed, corrected, doubtful or filled, with vPIC's original value kept.

NameTypeReqDescription
transmissionstring–Transmission, when the owner knows it and the VIN does not say. Applies to fuel economy only when EPA lists the model with both; without it an automatic is assumed and marked (fuel_economy.assumed, a…
vinstringyes17-character Vehicle Identification Number

No output schema declared.

No examples provided.

defect_investigations ~62

Search NHTSA model-year defect investigations with retained source variants and snapshot dates.

NameTypeReqDescription
limitinteger––
makestringyes–
modelstringyes–
offsetinteger––
yearintegeryes–

No output schema declared.

No examples provided.

epa_vehicle ~30

Get an explicitly selected EPA test configuration; not an exact VIN match.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

explore_capabilities ~17

Discover supported features and explicit coverage gaps.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fuel_price_assumptions ~21

EPA fuel-price assumptions, not local station prices.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_output_preferences ~27

Get the user's VIN report output preferences.

NameTypeReqDescription
user_tokenstringyesJWT token

No output schema declared.

No examples provided.

list_saved_vins ~41

List VINs saved by a user. Requires a user_token from /api/auth/login.

NameTypeReqDescription
user_tokenstringyesJWT token from website login

No output schema declared.

No examples provided.

lookup_recalls ~82

Look up recalls for a vehicle. Provide either a VIN or make/model/year.

NameTypeReqDescription
makestring–Vehicle make (e.g. Honda)
modelstring–Vehicle model (e.g. Civic)
vinstring–VIN to look up recalls for
yearnumber–Model year (e.g. 2020)

No output schema declared.

No examples provided.

manufacturer_communications ~61

Search indexed NHTSA communications, with source coverage. Bulletins are not recalls.

NameTypeReqDescription
limitinteger––
makestringyes–
modelstringyes–
offsetinteger––
yearintegeryes–

No output schema declared.

No examples provided.

owner_reported_mpg ~35

Voluntary owner-reported MPG for an EPA configuration, including sample size and limitations.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

ownership_scenario ~78

Calculate fixed-rate payments and optional ownership costs from explicit assumptions; not lender or tax quotes.

NameTypeReqDescription
aprnumberyes–
down_paymentnumber––
feesnumber––
monthsintegeryes–
ownershipobject––
pricenumberyes–
tax_amountnumber––

No output schema declared.

No examples provided.

remove_saved_vin ~42

Remove a VIN from the user's saved collection.

NameTypeReqDescription
user_tokenstringyesJWT token from website login
vinstringyesVIN to remove

No output schema declared.

No examples provided.

save_vin ~64

Save a VIN to a user's collection with an optional label.

NameTypeReqDescription
labelstring–Custom label (e.g. "Dad's truck")
user_tokenstringyesJWT token from website login
vinstringyes17-character VIN to save

No output schema declared.

No examples provided.

update_output_preferences ~117

Update which sections appear in VIN reports.

NameTypeReqDescription
show_complaintsboolean––
show_engineboolean––
show_fuel_economyboolean––
show_overviewboolean––
show_photosboolean––
show_raw_nhtsaboolean––
show_recallsboolean––
show_safety_equipmentboolean––
show_safety_ratingsboolean––
user_tokenstringyesJWT token

No output schema declared.

No examples provided.

validate_vin ~29

Quickly validate a VIN without calling any external APIs.

NameTypeReqDescription
vinstringyesVIN to validate

No output schema declared.

No examples provided.

vehicle_catalog ~51

Browse EPA year, make, model and configuration menus. Not sale listings.

NameTypeReqDescription
levelstringyes–
makestring––
modelstring––
yearinteger––

No output schema declared.

No examples provided.

vehicle_dimensions ~43

Canadian model-variant dimensions in cm and kg. Not VIN-specific.

NameTypeReqDescription
makestringyes–
modelstringyes–
yearintegeryes–

No output schema declared.

No examples provided.

vehicle_emissions ~26

Get EPA emissions for an explicit EPA vehicle ID.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

vin_recall_status ~160

VIN-specific manufacturer-reported open and completed recall status. Tesla and Ford open/completed states; GM completed/closed states with explicit repair dates where supplied; Honda and Acura active safety recalls; Subaru completed/incomplete safety recalls; Volkswagen, Audi, Land Rover and Jaguar recalls as reported by each maker; Nissan positive open safety recalls; Mopar positive open records matched to the full VIN. Service programs are separate. Toyota, Hyundai and Kia require interactive official verification. Unknowns are never zero. Not a complete service history. Where the maker's reply describes the VIN (Volkswagen, Audi, Land Rover, Jaguar, Subaru, Honda/Acura), manufacturer_description gives the raw text and only the fields it states.

NameTypeReqDescription
vinstringyes–

No output schema declared.

No examples provided.

Install

How do I install the VIN MCP server?

VIN MCP is a hosted endpoint at https://mcp.vin/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.vin

# add to Claude Code
claude mcp add --transport http keptlive-vin-mcp 'https://mcp.vin/mcp'
Common questions

What is the VIN MCP server?

VIN MCP is listed in the public MCP registry as io.github.keptlive/vin-mcp. Free VIN decoder: NHTSA specs, recalls, complaints, safety ratings, EPA fuel economy. No API key. This page covers its hosted endpoint (https://mcp.vin/mcp).

Is the VIN MCP server safe to use?

VIN MCP scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VIN MCP server expose?

VIN MCP exposes 22 tools: decode_vin, validate_vin, lookup_recalls, batch_decode, explore_capabilities, and 17 more. Their descriptions and schemas cost roughly 1,292 tokens of context every time the server is loaded.

Does the VIN MCP server require authentication?

No. We connected to VIN MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VIN MCP server still maintained?

VIN MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the VIN MCP server?

VerifyMCP ran 13 checks on VIN MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.