resolve_vehicleVIN · Year · Make · Model · Trim · Engine · Drivetrain · Configuration resolution
AUTO411 Vehicle Intelligence MCP
Vehicle data that knows when it has the right car. Resolve by VIN or Year / Make / Model, then retrieve normalized specifications, tires and wheel fitment, safety and EPA efficiency through MCP.
2016 Scion FR-S · configuration 627260Normalized individual facts returned after vehicle identity is safely resolved.
Built to become part of the workflow
An identity-first automotive MCP server and vehicle intelligence API for AI-agent developers, repair and service software, vehicle research, fleets, and tire, wheel or parts applications.
Five focused tools
The MCP server keeps vehicle resolution separate from configuration-dependent facts, so an agent knows when it can answer and when it should ask for another detail.
resolve_vehicleVIN · Year · Make · Model · Trim · Engine · Drivetrain · Configuration resolution
get_vehicle_specsEngine · Displacement · Cylinders · Horsepower · Transmission · Drivetrain · Fuel type
get_vehicle_fitmentOEM tire sizes · Bolt pattern / PCD · Center bore · Wheel offset · Thread / lug size
get_vehicle_safetyRecalls · Owner complaints · Investigations · Manufacturer communications · Available safety information
get_vehicle_efficiencyEPA city MPG · Highway MPG · Combined MPG · Fuel type · EV information where available
Identity before specifications
Automotive data is often configuration-dependent. AUTO411 reports identity, availability and evidence status explicitly instead of filling an ambiguous or missing field with a guess.
MATCHED_SINGLEThe requested vehicle has one supported identity and appropriately scoped facts can be returned.
NEEDS_IDENTITYMore than one configuration remains. This is an intentional result: ask for a distinguishing detail before using configuration-dependent facts.
NO_MATCHAUTO411 does not substitute a nearby vehicle or invent an answer when reliable identity evidence is unavailable.
Real workflows
Use AUTO411 as an automotive MCP server, VIN lookup API or vehicle intelligence layer for agent and application workflows.
Submit a VIN to resolve the supported vehicle identity. Retrieve normalized vehicle specs only when the result is safe to use.
VIN→MATCHED_SINGLE→SPECSAsk for available NHTSA safety information at its stated scope, or EPA efficiency data after the relevant vehicle identity is resolved.
VEHICLE→SAFETY / EPADeveloper access
Coverage varies by vehicle, configuration and data category. Missing information stays missing, and ambiguous identity stays explicit.
Build with the 411
Connect AUTO411 Vehicle Intelligence through MCP.
Get MCP Access