MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
CARVECTOR_API_KEYAPI keyrequiredYour CarVector API key (free at carvector.io)
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
search_vehiclesSearch the CarVector catalog by year, make, and/or model. Returns matching vehicles with their id and specs. Use this first to resolve a vehicle id, then call get_vehicle or get_recalls with that id.Search the CarVector catalog by year, make, and/or model. Returns matching vehicles with their id and specs. Use this first to resolve a vehicle id, then call get_vehicle or get_recalls with that id.
No input schema was published for this tool.
get_vehicleGet full specifications for one vehicle by its id (an opaque token returned by search_vehicles). Returns engine, drivetrain, body details, a representative image, and recall count.Get full specifications for one vehicle by its id (an opaque token returned by search_vehicles). Returns engine, drivetrain, body details, a representative image, and recall count.
No input schema was published for this tool.
get_recallsGet federal recall campaigns for a vehicle by its id. Returns each campaign with component, summary, consequence, and remedy.Get federal recall campaigns for a vehicle by its id. Returns each campaign with component, summary, consequence, and remedy.
No input schema was published for this tool.
lookup_dtcLook up an OBD-II diagnostic trouble code (e.g. P0420). Returns the code title, category, severity, and safety/emissions flags. Reference only — does not include repair cost estimates.Look up an OBD-II diagnostic trouble code (e.g. P0420). Returns the code title, category, severity, and safety/emissions flags. Reference only — does not include repair cost estimates.
No input schema was published for this tool.
get_complaintsGet the owner-complaint signal for a vehicle by its id: an aggregate (totals by component and year, plus crash/fire/injury counts) and the most-recent complaints. Requires a Pro plan or higher.Get the owner-complaint signal for a vehicle by its id: an aggregate (totals by component and year, plus crash/fire/injury counts) and the most-recent complaints. Requires a Pro plan or higher.
No input schema was published for this tool.
get_tsbsGet the manufacturer technical service bulletin (TSB) index for a vehicle by its id — bulletin metadata (id, date, type, affected components, summary), not the documents themselves. Requires a Business plan or higher.Get the manufacturer technical service bulletin (TSB) index for a vehicle by its id — bulletin metadata (id, date, type, affected components, summary), not the documents themselves. Requires a Business plan or higher.
No input schema was published for this tool.
get_investigationsGet federal defect investigations for a vehicle by its id — a leading indicator that often precedes recalls. Returns each action with subject, component, open/close dates, and status. Requires a Business plan or higher.Get federal defect investigations for a vehicle by its id — a leading indicator that often precedes recalls. Returns each action with subject, component, open/close dates, and status. Requires a Business plan or higher.
No input schema was published for this tool.
7 of 7 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+41 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.