🧰 Vehicle VIN Decoder MCP Server

An MCP server over the official NHTSA vPIC API (vpic.nhtsa.dot.gov) — decode a Vehicle Identification Number into make, model, year, body, engine, plant and manufacturer. Built for insurance intake and vehicle-onboarding workflows. Runs as an Apify Standby MCP server; connect an MCP client at path /mcp.

This is a standby MCP server: it stays warm on Apify and answers tool calls from any MCP client (Claude Desktop, Cursor, an agent framework) at https://nexgenwatch--vehicle-vin-decoder-mcp.apify.actor/mcp. Billing is pay-per-event: $0.05 when the server starts, then $0.05 per tool call (mcp-tool-call). Source: vpic.nhtsa.dot.gov.

No login, no source API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

A standby server answers tool calls rather than writing a dataset, so the sample is the server's own live health answer (GET https://nexgenwatch--vehicle-vin-decoder-mcp.apify.actor/, HTTP 200, read on 2026-09-17) followed by its tool table:

{
  "server": "vehicle-vin-decoder",
  "billing_gate": true,
  "declared_events": [
    "apify-actor-start",
    "mcp-tool-call"
  ],
  "scope": "The official NHTSA vPIC API (vpic.nhtsa.dot.gov): VIN decoding for US-market vehicles — make, model, year, body, engine, plant and manufacturer.",
  "rate_limit_per_sec": 5.0,
  "rate_waits": 0,
  "ready": true
}

Tool	Arguments	What it returns
decode_vin	vin: str, model_year: int = 0	Decode a Vehicle Identification Number via NHTSA vPIC. Returns make, model, year, body, engine, plant and manufacturer. A VIN NHTSA cannot validate is a sourced 'invalid' answer with its ErrorCode/ErrorText — not a failu
explain_limits	``	What this server can and cannot tell you about VIN decoding.

✅ What you get

2 tools, each returning a JSON object built only from what the source answered, with a scope and note field stating what the source does and does not cover. A lookup the source answers with 'not found' is a sourced answer (charged); malformed input or a source failure returns a notice that is NOT charged; nothing is ever fabricated.

Tools

• decode_vin(vin, model_year?) — decode a VIN. A VIN NHTSA cannot validate returns a sourced "invalid" answer with its ErrorCode/ErrorText.
• explain_limits() — scope, the invalid-is-an-answer rule, and what the server will not return.

Billing

Event	Price
Server start (apify-actor-start)	$0.05, charged once per run by the platform
Tool call (mcp-tool-call)	$0.05 per completed tool call

One flat charge per completed tool call. A clean decode and a sourced "invalid VIN" (NHTSA ErrorCode != 0) are both completed answers and are charged. An input too short/empty to be a VIN, or an upstream NHTSA failure, is a notice and is not charged.

Source

The official NHTSA vPIC API, queried anonymously (no key). vPIC is build data only — no title, ownership, accident or theft history. Coverage is strongest for US-market vehicles.

⚙️ Sample inputs

1. Connect an MCP client (Claude Desktop / Cursor style config; your Apify API token goes in the header):

{
  "mcpServers": {
    "vehicle-vin-decoder-mcp": {
      "url": "https://nexgenwatch--vehicle-vin-decoder-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

2. One tool call over JSON-RPC (what the client sends to /mcp; each call is one mcp-tool-call event):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "decode_vin",
    "arguments": {
      "vin": "<vin>",
      "model_year": 0
    }
  }
}

3. Health check from a shell (free — no tool call is charged):

$curl -H "Authorization: Bearer $APIFY_TOKEN" https://nexgenwatch--vehicle-vin-decoder-mcp.apify.actor/

🧾 JSON sample record

The live health record above is the server's own answer; a tool result carries the fields listed in the tool table plus scope and note.

🔧 How it works

Source. vpic.nhtsa.dot.gov — endpoints: https://vpic.nhtsa.dot.gov/api/vehicles. Public, logged-out reads only.

Standby. Apify keeps one server process warm; each MCP session is served by that process and idle servers are stopped by the platform. Nothing is cached between calls except what the source itself caches.

Charging. Every tool call charges one mcp-tool-call at $0.05 through Apify's pay-per-event billing before the answer is returned; the declared events are asserted against the live pricing at startup (billing_gate in the health answer).

What is not done. No login, no CAPTCHA bypass, no private data, no scraping of pages the source does not publish to any visitor.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.05	$0.05	$0.05	$0.05
Tool call (mcp-tool-call)	$0.05	$0.05	$0.05	$0.05

• 10 tool calls in one session: $0.05 start + 10 × $0.05 = $0.55
• 100 tool calls in one session: $0.05 start + 100 × $0.05 = $5.05
• 1000 tool calls in one session: $0.05 start + 1000 × $0.05 = $50.05

A health check or a connection that makes no tool call charges only the $0.05 start fee. A sourced 'not found' answer is a completed tool call and is charged; a notice for malformed input or a source failure is not charged (settle() charges only chargeable outcomes).

⚖️ Legal & ToS

The server reads public data published by vpic.nhtsa.dot.gov to any visitor, identifies itself with a contact User-Agent, and does not access accounts or private data. Use the answers in line with the source's terms and your local law; the intended use is B2B research and agent tooling.

❓ FAQ

Q: Do I need a source API key?
A: No. vpic.nhtsa.dot.gov is read logged-out. You need only your Apify API token to connect to the server.

Q: Which MCP clients work?
A: Any client that speaks the MCP HTTP transport: Claude Desktop, Cursor, Windsurf, LangChain/LlamaIndex MCP adapters and Apify's own MCP client. Point it at the /mcp URL above.

Q: What happens when the source has no answer?
A: A sourced 'not found' (for example a 404 for an unknown identifier) comes back as an answer with scope and note explaining what was checked (where the server carries those fields), and is charged as a completed call; malformed input or a source outage returns a notice that is not charged. Nothing is invented.

Q: How is a call billed?
A: One mcp-tool-call event per tool call at $0.05, plus $0.05 when the server starts. Idle time is not billed to you.

Q: Is it rate limited?
A: The server paces requests to the source and answers calls in the order they arrive.

Q: Can I call it without an MCP client?
A: Yes — the /mcp endpoint is plain JSON-RPC over HTTP (sample input 2), and GET / is a free health check.

🆘 Troubleshooting

• 401 / 403 from the server → the Authorization header is missing or the token is wrong → use Bearer <your Apify API token>.
• 400 Missing session ID → the client hit /mcp without initialising an MCP session → let the MCP client connect (it performs the handshake); raw JSON-RPC needs the session header the initialise call returns.
• Tool returns a notice instead of data → the input was malformed or empty, or the source failed → the call was not charged; check the note/reason field, fix the input and call again.
• First call is slow → the standby server was cold and Apify started it → later calls in the same session are fast.

🔗 Related Actors

• UK Competition Case MCP Server — Answer 'is there a UK competition case touching these companies or this market' from the Competition and Markets Authority case register, with an exp…
• UK Parliament Stakeholder MCP Server — An MCP server over the official UK Parliament Members API (members-api.parliament.uk) —
• UK Planning Constraints MCP Server — An MCP server over the official planning.data.gov.uk platform — ~220 national planning
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this server answered a question your agent could not, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.