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 分