Carvector Mcp

io.github.carvectorio由 GitHub 帳號 carvectorio 發布v1.1.1更新於 Oct 24, 2026

Vehicle specs, federal recalls, complaints, TSBs, investigations and OBD-II DTC data for AI agents.

已驗證STDIO僅桌面位置與生活

概覽

AI 產生的概覽

讓助理透過 CarVector API 查詢車輛規格、聯邦召回、車主投訴、服務公告、缺陷調查與 OBD-II 故障碼。

可以做什麼
這是一個輕量本機用戶端,會把每次請求轉送到 CarVector API,回傳結構化、可溯源的車輛資料。工具涵蓋依年份、品牌、車型搜尋車輛,單一車輛的完整規格,聯邦召回活動,依元件彙總的車主投訴,製造商技術服務公告索引,聯邦缺陷調查,以及 OBD-II 診斷故障碼參考。助理通常會先解析出車輛 id,再串接其他查詢。
適用情境
當助理需要真實的汽車參考資料,而不是憑空猜測的規格、召回狀態或故障碼意義時適用。適合服務顧問助理、消費者汽車聊天機器人,以及需要把結構化車輛知識當成工具的汽車類代理。
執行需求
透過 stdio 在本機執行,通常以 npx 從 npm 套件 carvector-mcp 啟動,因此需要 Node.js。需要 CarVector API 金鑰,透過 CARVECTOR_API_KEY 環境變數提供;沒有金鑰用戶端會結束。有免費額度,部分工具僅限付費方案。需要能連線到 CarVector API 主機的網路。
安裝前請注意
API 金鑰屬於憑證:README 建議使用 CARVECTOR_API_KEY 環境變數,因為以命令列參數傳入可能會在行程列表中曝光。每次呼叫都會轉送到第三方 CarVector API,並計入方案的速率限制。投訴、服務公告與調查等部分工具需要付費方案。README 聲稱用戶端只把金鑰送到一個主機且沒有遙測,但這只是廠商自己的說法。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Carvector Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

carvector-mcp

Give your AI agent real vehicle data. An MCP server that lets Claude, Cursor, ChatGPT, or any MCP-capable client query the CarVector API natively — vehicle specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II diagnostic trouble codes.

Models hallucinate car data. They invent horsepower numbers, miss recalls filed last week, and guess at what a trouble code means. carvector-mcp gives your agent structured, sourced answers it can cite instead of a confident guess.

npx -y carvector-mcp --key cv_your_key

[npm] · MIT · Free tier, no card → carvector.io


Quickstart

1. Get a free API key at carvector.io — 500 requests a month, no credit card.

2. Add it to your MCP client. Most clients use an mcpServers block:

json
{  "mcpServers": {    "carvector": {      "command": "npx",      "args": ["-y", "carvector-mcp"],      "env": { "CARVECTOR_API_KEY": "cv_your_key" }    }  }}

That's it. Restart your client and ask it about a vehicle.

Prefer a remote server? If your client supports HTTP MCP, skip the install and point it straight at the hosted endpoint:

json
{ "mcpServers": { "carvector": {    "url": "https://api.carvector.io/v1/mcp",    "headers": { "Authorization": "Bearer cv_your_key" } } } }

Tools

ToolWhat it returns
search_vehiclesMatching vehicles by year / make / model, with ids + specs
get_vehicleFull specs for one vehicle — engine, drivetrain, body, image, recall count
get_recallsFederal recall campaigns for a vehicle — component, summary, consequence, remedy
get_complaintsOwner-complaint signal for a vehicle — aggregate by component + the most recent complaints (Pro plan)
get_tsbsManufacturer service-bulletin index for a vehicle — the fix the dealer already knows about (Business plan)
get_investigationsFederal defect investigations for a vehicle — a leading indicator of recalls (Business plan)
lookup_dtcAn OBD-II code's title, category, severity, and safety/emissions flags

The agent chains them naturally: search_vehicles to resolve an id, then get_vehicle, get_recalls, get_complaints, get_tsbs, or get_investigations.


Example

You: "Is a P0300 code serious?"

js
→ carvector.lookup_dtc({ code: "P0300" }){  "code": "P0300",  "title": "Random/Multiple Cylinder Misfire Detected",  "category": "Powertrain",  "severity": "High",  "safety_risk": true,  "emissions_related": true}

Your agent answers: "Yes — P0300 is a high-severity, safety-related misfire code. Don't keep driving on it." Sourced, not guessed.


Three things to build with it

  • A service-advisor copilot that pulls a customer's exact trim, open recalls, the manufacturer's documented fix (TSBs), the complaint pattern behind a symptom, and a decoded check-engine code — in one turn, no tab-switching.
  • A consumer car chatbot that answers "what engine does my truck have" and "is it under recall" with real data instead of a hallucination.
  • A coding/automotive agent that needs structured vehicle knowledge as a tool, not a wall of scraped text to parse.

Paying per call instead of using a key (x402)

The CarVector HTTP API also accepts x402 payments, so an agent with a wallet can call it with no account, no signup and no API key — it pays per request and gets the data back.

  • $0.01 USDC per call, on Base mainnet (USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
  • Request a paid endpoint without payment and you get an HTTP 402 with everything needed to pay and retry:
bash
curl -i "https://carvector.io/v1/vehicles?year=2020&make=Ford&model=F-150"# HTTP/1.1 402 Payment Required# { "x402Version": 1, "accepts": [ { "scheme": "exact", "network": "base", ... } ] }

Payable endpoints: /v1/vehicles, /v1/vehicles/:id, /v1/vehicles/:id/recalls, /v1/vehicles/:id/complaints, /v1/vehicles/:id/tsbs, /v1/vehicles/:id/investigations, /v1/dtc/:code.

This MCP client does not pay — it uses an API key. carvector-mcp requires CARVECTOR_API_KEY and exits without one. x402 is for calling the HTTP API directly. If you want keyless access from an agent, call the endpoints above rather than going through this package.

About the data

carvector-mcp is an open-source, thin client. It bundles no data — every call forwards to the CarVector API, authenticated with your key. What you get back:

  • Vehicles — a broad catalog (1925–2029), broken out by trim and engine variant, with representative illustrations (not photos).
  • Recalls — federal recall campaigns mapped to year / make / model.
  • Complaints — owner-filed complaints aggregated by component (with crash / fire / injury counts) plus the most recent filings, mapped to a vehicle. (Pro plan.)
  • Service bulletins (TSBs) — the manufacturer's technical service-bulletin index — metadata, not the documents. (Business plan.)
  • Investigations — federal defect investigations, a leading indicator that often precedes a recall. (Business plan.)
  • DTC reference — OBD-II codes classified by category, severity, and safety/emissions flags. Reference only — repair-cost economics is on the roadmap, not in responses today.

Calls count against your plan's rate limit and show up in your dashboard, exactly like a REST request.


Open source & your key

This client is ~150 lines of readable JavaScript — please read them. It:

  • talks to one host only — api.carvector.io (grep index.js, it's the only URL),
  • sends your key only as a Bearer header to that host, nowhere else,
  • has zero telemetry, analytics, or phone-home, and writes nothing to disk,
  • depends on exactly one package: the official @modelcontextprotocol/sdk.

Your key stays on your machine. Set it via the CARVECTOR_API_KEY env var (preferred); --key works too but, like any CLI argument, is visible in process listings.

License

MIT. The client is open source; the data is served by CarVector.

來源:README.md,提交 a3657e3

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

2
  1. v1.1.1最新Sep 19, 2026
  2. v1.0.1Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分