Vehicle VIN Decoder MCP Server avatar

Vehicle VIN Decoder MCP Server

Pricing

from $50.00 / 1,000 tool calls

Go to Apify Store
Vehicle VIN Decoder MCP Server

Vehicle VIN Decoder MCP Server

An MCP server over the official NHTSA vPIC API (vpic.nhtsa.dot.gov) — decode a Vehicle

Pricing

from $50.00 / 1,000 tool calls

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

3 days ago

Last modified

Categories

Share

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.

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

EventPrice
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.