vin-decode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIN_MCP_DB_PATH | No | Path to the curated_vpic.db database file. Overrides the default database location. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| decode_vinA | Decode a VIN to make, model, year, and vehicle type. Returns the decoded make, model, model year, and vehicle type for a 17-character VIN. Uses the NHTSA vPIC pattern database for make/model resolution. Model year is computed from VIN position 10 unless you provide model_year explicitly. Partial VINs (shorter than 17 characters) may still decode if the WMI (positions 1-3) matches a known manufacturer. |
| decode_partial_vinA | Decode a partial VIN pattern with wildcards. Supports * as a wildcard for exactly one character (matching the vPIC pattern format). Useful for matching a VIN you don't have the full 17 characters of, or for pattern-based lookups. |
| get_all_makesA | List all vehicle makes registered in vPIC. Returns every make currently in the curated database. This includes makes from all vehicle types (cars, trucks, motorcycles, etc.) that passed the curation filter. Returns: List of dicts with keys: id, name. Sorted alphabetically by name. |
| get_models_for_makeA | List all models for a given make. Optionally filter by vehicle type to narrow results (e.g. get only car models or only motorcycle models for a make that produces both). |
| get_model_yearsA | Get the model year range for a make/model pair. |
| get_wmi_infoA | Decode a World Manufacturer Identifier (WMI). Returns manufacturer information for a 3- or 6-character WMI code (VIN positions 1-3, optionally + positions 12-14 for low-volume manufacturers). |
| get_vehicle_typesA | List all available vehicle types. Returns the vehicle types in the curated dataset (e.g. Passenger Car, Motorcycle, Truck, MPV, Off-Road Vehicle). Returns: List of dicts with keys: id, name. |
| get_make_vehicle_typesA | List the vehicle types a given make produces. Useful for understanding what categories a manufacturer covers (e.g. BMW produces "Motorcycle", "Passenger Car", "Truck"). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_schema | Database schema and column descriptions. This resource exposes the full DDL for the VIN database and documentation for each column. Useful for LLMs that need to understand the data structure. Tables: make — Vehicle makes (manufacturers) model — Vehicle models vehicletype — Vehicle type categories make_model — Linking table: which models belong to which makes, and under which vehicle type model_years — Production year ranges for each make/model pair wmi — World Manufacturer Identifiers (3 or 6 characters) wmi_vinschema — WMI to VIN schema mapping with year ranges vin_pattern — VIN descriptor patterns used for make/model resolution dataset_info — Metadata about this database version and build |
| get_info | Dataset information and build metadata. Returns the source file, vintage date, build timestamp, script version, and dataset statistics for this database instance. |
TDQS
Scored across 8 tools
Most tools are clearly separated by resource and action: decode_* covers VIN/WMI decoding, get_* covers lookup tables. The only potential confusion is between decode_vin and decode_partial_vin, since decode_vin already accepts short VINs, though the wildcard/pattern use case is explicitly distinguished.
All tool names follow a consistent verb_noun pattern starting with decode_ or get_, and resource nouns are used predictably. The naming makes the set easy to scan and understand.
Eight tools is well-scoped for a VIN decoding and vehicle reference server. Each lookup tool has a clear purpose and the count is neither too sparse nor bloated.
The server covers the core VIN decode workflow (full and wildcard partial VINs, WMI info) and the supporting reference queries needed to explore makes, models, model years, and vehicle types. There are no obvious dead ends for the stated domain.