The vehicle data MCP server
for AI agents.
Paste one config block and Claude, Cursor or your internal copilot can search the catalog, read specs, check live recalls and find tire fitment — as native tools, grounded in 1,342,720 real records, with the same token as the REST API.
MCP calls share your plan's API quota — the free tier includes 100 calls/mo, no card.
What is the VehDB MCP server?
A hosted bridge between AI agents and a real, enriched vehicle database.
The Model Context Protocol (MCP) is an open standard for connecting AI agents to external tools and
data. VehDB runs a hosted MCP server at https://mcp.vehdb.com/mcp
that exposes our cleaned, cross-referenced vehicle database — 853,870 cars,
233,450 motorcycles, 84,300 boats and
171,100 tire fitments, enriched with EPA fuel economy and live NHTSA recalls — to any
MCP-compatible client.
Instead of scraping pages, pasting spec sheets into a prompt, or hand-writing function-calling schemas, you paste one config block. The agent discovers every tool automatically and starts answering questions with structured, current data — the same data, same token and same quota as the REST API and the dashboard workspace.
Sixteen tools. Real answers.
Typed inputs, JSON output — the model calls them directly, no prompt gymnastics.
search_vehicles
Search cars, motorcycles, boats or tire sizes by make, model, year, body, fuel and drivetrain — the agent resolves any vehicle the user mentions.
get_vehicle
Fetch a single record by type and UUID — full specifications plus EPA economy in one call.
recalls_for_vehicle
Live NHTSA recall campaigns, open defect investigations and the NCAP crash-test rating for a car or motorcycle; for a boat, the U.S. Coast Guard recalls filed under its builder's codes.
service_bulletins_for_vehicle
NHTSA manufacturer communications for a model year: service bulletins, warranty extensions and special coverage, over-the-air updates, with the most named components.
complaints_for_vehicle
NHTSA owner-complaint statistics by component and model year — the reliability signal that precedes recalls.
model_year_scorecard
Every model year of one make/model side by side — complaints with a percentile against the same model year, recalls, investigations, NCAP stars, fatal-crash involvement and mpg — with the best and worst year called out.
vehicle_insights
Aggregate reports without record sweeps: most complained-about vehicles, fatal-crash rankings by vehicle and body class, engine trends, Canadian fuel economy, recall age, rim sizes and FARS-vs-CRSS crash severity.
tire_sizes_for_vehicle
OEM and alternate tire sizes that fit a given make/model/year, with computed geometry (±3%).
vehicles_for_tire_size
Reverse fitment: every vehicle that runs a tire size as OEM or as an accepted alternate.
decode_vin
Decode a VIN with NHTSA vPIC and get the matching VehDB cars, motorcycles and tire fitments by uuid.
my_lists
The user's saved vehicles — the same lists curated in the dashboard, with notes and part numbers.
api_usage
The plan, rate limit and how much of this month's call and record quota is left.
resolve_vehicle
A vehicle as the user typed it, in the catalogue's spelling and in the spellings NHTSA files its recalls under.
decode_hin
Decode a boat's Hull Identification Number: the builder from its U.S. Coast Guard code, the build month, model year and the builder's recalls; with include_history, the accidents and documentation record reported under the hull.
tire_dot_check
Read a tire's DOT code: the plant, the week it was made, its age and the NHTSA tire recalls covering that plant and week.
energy_prices
Latest EIA gasoline, diesel and electricity prices for a state, with a yearly fuel cost for any mpg.
Tool reference
Each tool is typed and self-describing — the agent reads the schema, you don't write one.
| Tool | Inputs | Returns |
|---|---|---|
search_vehicles |
type, make, model, year, limit, page |
Paginated matching records with core specs |
get_vehicle |
type, uuid |
Full specifications + EPA economy fields |
decode_vin |
vin |
Decoded VIN fields + matching car, motorcycle and tire-fitment uuids |
recalls_for_vehicle |
car, motorcycle or boat uuid (or make, model, year, or vin) |
Live NHTSA recall campaigns, open investigations + NCAP rating; USCG recalls for a boat |
service_bulletins_for_vehicle |
car or motorcycle uuid (or make, model, year) |
Counts by type, most named components, warranty extensions, latest communications |
complaints_for_vehicle |
make, model, year |
Complaint totals, top components, trend by year, neighbouring model years |
model_year_scorecard |
make, model |
Per model year: trims, mpg, complaints + percentile, top component, recalls, investigations, NCAP, FARS/CRSS crashes, best and worst year |
vehicle_insights |
report, year / make / model, year_min, year_max |
Ranked or trended rows for the chosen report, sources labelled |
tire_sizes_for_vehicle |
make, model, year, page |
OEM + alternate sizes, with the fitment disclaimer |
vehicles_for_tire_size |
size, make, year, page |
Vehicles running the size as OEM or alternate |
my_lists |
page (uses the token owner) |
The user's saved lists with notes |
api_usage |
— (uses the token owner) |
Plan, rate limit, calls and records used this month |
resolve_vehicle |
q, year |
Catalogue make/model spelling + the NHTSA spellings (nhtsa_match) |
decode_hin |
hin |
Builder (USCG code), serial, build month and year, model year, catalogue makes, builder recalls |
tire_dot_check |
tin, size, brand |
Plant, build week and year, age, matching NHTSA tire recalls, with the disclaimer |
energy_prices |
state, mpg, fuel_type |
Weekly fuel and monthly electricity prices; annual fuel cost for the mpg |
The same records are available over the REST API — see the full docs.
Ask it anything about a vehicle
Questions your AI agent can answer with VehDB
Connect VehDB to Claude, ChatGPT or Cursor and ask in plain words. The agent picks the tools; the answers below are computed from today's data.
recalls_for_vehicle
- Recall campaigns
- 23
- Open investigations
- 5
- Newest
- 2026-05-04
From today's VehDB data: NHTSA, EPA and the vehicle catalogue.
model_year_scorecard
- Best year
- 2022
- Worst year
- 2007
- Years compared
- 25
From today's VehDB data: NHTSA, EPA and the vehicle catalogue.
search_vehicles
get_vehicle
- Combined MPG
- 51
- Fuel cost / yr
- $1,300
- CO₂
- 173 g/mi
From today's VehDB data: NHTSA, EPA and the vehicle catalogue.
tire_sizes_for_vehicle
- Most common
- 275/60R20
- OEM sizes
- 8
From today's VehDB data: NHTSA, EPA and the vehicle catalogue.
vehicle_insights
- Fatal-crash vehicles
- 14
- Occupant deaths
- 8
From today's VehDB data: NHTSA, EPA and the vehicle catalogue.
vehicle_insights
- Ford
- 135 campaigns
- Vehicles in them
- 12,632,844
From today's VehDB data: NHTSA, EPA and the vehicle catalogue.
my_lists
recalls_for_vehicle
decode_vin
tire_sizes_for_vehicle
recalls_for_vehicle
Enriched data
What comes back with every answer
One vehicle, every public record joined to it: specs from the catalogue, economy and emissions from the EPA, safety from NHTSA. Counts are live.
- engine
- drive
- transmission
- body
- doors
- markets
search_vehicles
- mpg city/highway
- EV range
- annual fuel cost
- CO₂ g/mi
get_vehicle
- smog rating
- SmartWay
- greenhouse-gas score
get_vehicle
- campaign
- component
- remedy
- do-not-drive
- build window
recalls_for_vehicle
- by component
- crashes
- fires
- injuries
- percentile
complaints_for_vehicle
- service bulletins
- warranty extensions
- over-the-air updates
- components
service_bulletins_for_vehicle
- open investigations
- NCAP stars
- front/side/rollover
- safety systems
recalls_for_vehicle
- fatal crashes
- occupant deaths
- injury-crash estimates
vehicle_insights
- OEM size
- alternate sizes
- diameter delta
- load & speed index
tire_sizes_for_vehicle
- make, model, year
- engine
- plant
- matching VehDB trims
decode_vin
- HIN decode
- builder
- model year
- USCG recalls
decode_hin
- plant
- build week
- tire age
- covering recalls
tire_dot_check
- gasoline grades
- diesel
- electricity by state
- annual fuel cost
energy_prices
- best & worst year
- complaint percentile
- flags
model_year_scorecard
An agent grounding its answer in vehicle data
One question, three tool calls, an answer backed by today's records.
user: "We're quoting a 2024 Camry. What tires fit it and are there open recalls?" agent → search_vehicles({ "make": "Toyota", "model": "Camry", "year": 2024 }) ← { "uuid": "a1b2c3d4-…", "trim": "SE", "fuel_type_name": "GASOLINE" } agent → tire_sizes_for_vehicle({ "uuid": "a1b2c3d4-…" }) ← { "oem": "235/45R18", "alternates": ["235/40R19", "245/45R18"] } agent → recalls_for_vehicle({ "uuid": "a1b2c3d4-…" }) ← { "open_recalls": 0, "ncap_overall": 5 } agent: "The 2024 Camry SE runs 235/45R18 from the factory (235/40R19 and 245/45R18 are common alternates). No open NHTSA recalls; NCAP overall 5/5."
Connected in three steps
No SDK, no webhook, no token to copy. Paste the URL, sign in, ask.
Paste one URL
In Claude, add VehDB from the app's connector directory in one click. Elsewhere, paste the URL as a custom connector or remote server (ChatGPT, Claude Code, Cursor, VS Code).
Approve it once
Your client opens a VehDB sign-in page (a free account works). Approve, and it connects with your team's plan.
Just talk to it
"What tires fit a 2024 Camry?" — the agent discovers the tools and calls them with live data. No prompting required.
https://mcp.vehdb.com/mcp
No token to copy: your client opens a VehDB sign-in page, you approve it once, and it connects.
-
1
Open VehDB in Claude's connector directory and click Connect.
-
2
Sign in to VehDB and choose Allow.
-
3
Turn VehDB on in a chat and ask away.
Add it by URL instead
-
1
Open Settings → Connectors and choose Add custom connector.
-
2
Name it VehDB and paste the server URL above. Leave the OAuth fields empty.
-
3
Click Connect, sign in to VehDB and choose Allow.
-
4
In a chat, turn VehDB on from the tools menu and ask away.
-
1
Open Settings → Apps & Connectors → Advanced and turn on Developer mode.
-
2
Create a connector: name VehDB, the server URL above, authentication OAuth.
-
3
Sign in to VehDB when asked and choose Allow.
-
4
Add VehDB to a chat from the tools menu.
-
1
Add the server:
claude mcp add --transport http vehdb https://mcp.vehdb.com/mcp
-
2
In Claude Code, run /mcp, pick vehdb and choose Authenticate. Your browser opens: sign in and choose Allow.
-
1
Add the server without a token:
{ "mcpServers": { "vehdb": { "url": "https://mcp.vehdb.com/mcp" } } } -
2
Cursor shows VehDB as Needs login. Click it, sign in to VehDB and choose Allow.
-
1
Add the server:
{ "servers": { "vehdb": { "type": "http", "url": "https://mcp.vehdb.com/mcp" } } } -
2
Start it from the file; VS Code asks you to sign in to VehDB. Choose Allow.
What you approve: the app can search the catalogue, read your team's saved lists and use your team's monthly quota. Calls count against the team selected in your dashboard, shown on the sign-in page. It never sees your password and cannot change your account.
Disconnect an app any time under Dashboard → MCP → Connected apps.
Use an API token instead (scripts, CI, clients without sign-in)
Create a token under Dashboard → API Tokens and send it as a Bearer header. The same token works for the REST API.
{
"mcpServers": {
"vehdb": {
"type": "http",
"url": "https://mcp.vehdb.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Why MCP beats scraping or hand-rolled function calling
The tools, schemas and auth are hosted and discovered — you maintain none of it.
Live, not embedded
Recalls change, model years land, fitments update. A tool call returns today's record — an embedding returns whenever you last indexed.
Structured, not hallucinated
Typed parameters and JSON responses. "Will 245/40R17 fit?" gets answered with computed geometry and live recall records — not a plausible guess.
Zero glue code
No scraper to babysit, no schemas to write, no vector DB to refresh. One hosted endpoint, one token, metered on the same quota as your API.
| Approach | Setup | Freshness | Maintenance |
|---|---|---|---|
| MCP server VehDB | One config block | Live, every call | None — hosted & discovered |
| Hand-rolled function calling | Write schema + wiring per tool, per client | Live, if you build it | You own schemas & updates |
| Pasted docs / scraping / RAG | Build a scraper or index | Stale since last index | Re-scrape & re-embed forever |
Works with your agent stack
Any MCP-compatible client over HTTP: sign in with OAuth, or send an API token.
Sign in with OAuth, or use a token
Clients that support MCP sign-in (Claude, ChatGPT, Claude Code, Cursor, VS Code) register themselves through OAuth 2.1 with dynamic client registration: you paste the URL, approve once on a VehDB consent page that names the app and the team it will bill, and disconnect it any time from your dashboard. Scripts and other clients send an API token as a Bearer header instead. Either way it is the same tools and the same plan quota as the REST API.
What teams build on the MCP server
A vehicle-grounded copilot in every workflow that touches cars, fitment or recalls.
Support copilots
Agents answer "what fits / is it recalled" from live records, not guesses.
Learn more →Underwriting assistants
Pull body class, safety rating and open recalls at quote time.
Learn more →Fleet copilots
Normalise mixed assets and surface fuel cost & recall exposure on demand.
Learn more →Parts & fitment bots
Resolve "will it fit" tire and wheel questions with computed geometry.
Learn more →Vehicle Data MCP FAQ
Common questions about the automotive MCP server.
See the API docs, the REST API, or the vehicle data for business guide.
Give your agent 1,342,720 vehicle records.
Paste the URL into your client, sign in, ask a question. MCP is included on every plan — starting with 100 calls/mo for free.
100 free API calls every month · REST API + MCP server on every plan · No card to start · See pricing