carwhere-vin-mcp
OfficialRelated Servers
Alternatives to carwhere-vin-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to look up US vehicle-safety data read-only — decoding VINs, and retrieving recalls, owner complaints, and 5-Star NCAP safety ratings by make, model, and year through NHTSA's public APIs.MIT
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that provides tools to decode vehicle VINs and check for open safety recalls using NHTSA's public APIs.MIT

auto-devofficial
AlicenseNot gradedqualityBmaintenanceEnables decoding VINs into complete vehicle specifications, searching active used car listings from US dealers, and retrieving vehicle valuations with total cost of ownership estimates.18 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables natural-language querying of NHTSA vehicle safety data, including VIN decoding, recall searches, consumer complaints, crash-test ratings, and defect investigations via MCP.398 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables querying vehicle registration information (BIN RENAVAM) from the official ECRVSP source. Read-only, prepaid per use, works with any MCP client.MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching current used car, truck, and motorcycle parts in the US, resolving vehicles via VIN, and retrieving part listings with source attribution, through read-only MCP tools.Apache 2.0
TDQS
Scored across 6 tools
decode_vin already returns pricing and NHTSA recalls inline, which overlaps heavily with the standalone get_pricing and check_recalls tools. An agent given a VIN could reasonably pick either path, and the descriptions don't clearly signal when to prefer the specialized tools over the bundled decode.
Most tools follow a clear verb_noun pattern (decode_vin, check_recalls, get_pricing, buy_vin_report). validate_vin_check_digit is longer but still verb-first, and about_carwhere breaks the verb_noun convention, which is a minor deviation.
Six tools is well-scoped for a VIN data service: each maps to a distinct step in the decode/recall/price/validate/purchase lifecycle with no filler.
The surface covers decoding, validation, recalls, pricing, and a paid full report, forming a sensible lifecycle. Minor gaps exist (e.g. no standalone history/ownership lookup), but the report tool largely fills those needs.