MCP docs

Connect your MCP client to VINState.

The MCP endpoint exposes VIN lookup as agent-callable tools. It uses the same Bearer API key, account limits, credits, and request logging as the VINState REST API.

Get MCP access MCP overview

Endpoint HTTP

POST https://vinstate.com/mcp
Authorization: Bearer sk-your-api-key
Content-Type: application/json

Client config

Use your API key as a Bearer token

Client configuration formats vary, but the endpoint and Authorization header are the only required VINState-specific values.

Example config

{
    "mcpServers": {
        "vinstate": {
            "url": "https://vinstate.com/mcp",
            "headers": {
                "Authorization": "Bearer sk-your-api-key"
            }
        }
    }
}

Tools

Available tool names

vin.decode_free

Free-tier friendly VIN lookup for demos, trials, and low-volume agent usage.

vin.decode

Production VIN lookup for paid and higher-volume MCP clients.

Input schema

One required argument

{
  "vin": "1HGCM82633A004352"
}

VINState trims and uppercases the VIN before validating it. Invalid VINs return a tool error result and are not billed.

JSON-RPC example

Call the decode tool

{
    "jsonrpc": "2.0",
    "id": "lookup-1",
    "method": "tools/call",
    "params": {
        "name": "vin.decode",
        "arguments": {
            "vin": "1HGCM82633A004352"
        }
    }
}

200-style tool result

Successful calls return MCP content blocks plus structured VIN data.

Tool errors stay structured

Invalid VINs, not-found records, and insufficient credits return isError=true.

Not billed on failures

Validation failures, not-found records, and supplier outages stay unbilled.

Visible in console

MCP calls are logged with channel=mcp for account review.