vin_decodeLABSCO SUMMARY
Three questions about a used car, answered from one number.
Specification, theft status and market value are the three things a VIN is usually looked up for, and all three sit behind one connection. The field-listing endpoint is free, which lets you see what a VIN will return before spending a paid call on it.
What it is
A Python MCP server over the Vincario API, exposing VIN decoding, stolen-vehicle checks and vehicle market valuation to an MCP client over streamable HTTP.
What you get
- A VIN decoded into detailed vehicle information
- The fields available for a given VIN listed first, through a free endpoint
- A check of whether the VIN appears in stolen-vehicle databases
- A market valuation for the vehicle, with odometer taken into account
- Stateless HTTP transport, so no session is held and it sits behind a proxy or load balancer without special handling
Requirements
A Vincario API key, passed as the X-API-Key HTTP header on each request. Run it in Docker, or locally with Python 3.11+ and uv; there is also a hosted endpoint at https://mcp.vincario.com/mcp. The local server listens on plain HTTP port 8080, so put a reverse proxy in front for HTTPS.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Finding out what a car actually is before you view it
Decode the VIN from the listing and read the specification rather than the seller's description.
02
Checking a car is not stolen
Run the VIN against stolen-vehicle databases before money changes hands.
03
Deciding whether the asking price is fair
Get the market valuation with the odometer reading included, then compare it against what is being asked.
04
Seeing what data exists for a VIN before paying for it
List the available fields through the free endpoint, then decide whether the full decode is worth the call.
4 tools
Listed in project docs. Your client may show a different list.
vin_decode_infostolen_checkvehicle_market_valueBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Docker (recommended), or Python 3.11+ with uv
- A Vincario API key, passed as the X-API-Key HTTP header
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
Setup
TERMINAL
git clone https://github.com/Vincario/MCP-vincario
cd MCP-vincarioRun it with Docker (recommended):
TERMINAL
docker build -t vincario-mcp .
docker run -p 8080:8080 vincario-mcpOr run it locally with Python 3.11+ and uv:
TERMINAL
pip install uv
uv sync
uv run main.pyEither way the server listens on http://localhost:8080.
Hosted endpoint
ENDPOINT URL
https://mcp.vincario.com/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"vincario": {
"type": "http",
"url": "http://localhost:8080",
"headers": {
"X-API-Key": "<YOUR_API_KEY>"
}
}
}
}
