MCPFax Vehicle Diagnostics MCP Server

by mcpscores Your server? Claim it

answering

MCPFax Vehicle Diagnostics is answering right now. Last checked 12 min ago. It exposes 4 tools.

A fault code, a VIN, or a recall — answered from public NHTSA and standards data.

Uptime history 63 days of history · worst day 93%

63 days agonow

100.0%

Uptime 24h

182 of 182 checks

Tools

read from the server

80 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 20

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 28 August 2026. No other catalogue keeps this.

5 Sep 4 tools changed the parameters they ask for dtc_lookup, vehicle_recalls, vehicle_tsbs and 1 more

5 Sep a tool changed version

4 Sep a tool changed version

31 Aug a tool description was rewritten vehicle_tsbs

28 Aug 8 tools disappeared find_service_bulletins, get_catalog_attributions, get_catalog_status and 5 more

28 Aug 4 tools appeared dtc_lookup, vehicle_recalls, vehicle_tsbs and 1 more

28 Aug a tool changed version

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add vehicle-fault-codes --transport http https://faultcode-diagnostic-mcp.bowling-anthony.workers.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "vehicle-fault-codes": {
      "url": "https://faultcode-diagnostic-mcp.bowling-anthony.workers.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.vehicle-fault-codes]
url = "https://faultcode-diagnostic-mcp.bowling-anthony.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "vehicle-fault-codes": {
      "url": "https://faultcode-diagnostic-mcp.bowling-anthony.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "vehicle-fault-codes": {
      "url": "https://faultcode-diagnostic-mcp.bowling-anthony.workers.dev/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

vehicle

vehicle_recalls

Official NHTSA safety recalls for a vehicle. Returns campaign id, affected component, the safety consequence, and the free remedy, newest first (max 50). Query by make (optionally model and year) or by a known campaign id. Use this before buying a used vehicle or when a customer asks whether their car has open recalls. A zero count means nothing matched the ingested NHTSA subset — it does not prove the vehicle is recall-free. Costs $0.005 USDC per call via x402 on Base.

vehicle_tsbs

NHTSA Technical Service Bulletins (manufacturer repair guidance for known defects that are not safety recalls). Returns bulletin id, summary, and the fault codes each bulletin names (max 50). Query by make/model/year, or by fault code to find bulletins that address that specific code. Use this after dtc_lookup when you want the manufacturer's documented fix. A zero count means nothing matched the ingested subset. Costs $0.005 USDC per call via x402 on Base.

dtc

dtc_lookup

Look up what a vehicle fault code (OBD-II diagnostic trouble code) means. Returns a reworded definition compiled from open/public sources (with the source and licence per row) plus which makes define the code specifically. Pass 'make' for the make-specific meaning instead of the generic SAE one — the same code can mean different things on different brands. Use this when a scan tool reported a code like P0301, B1318 or U0100; we never guess a meaning (unknown codes return not_found). Descriptions are compilations, not manufacturer verbatim strings, and severity is not guaranteed. Costs $0.006 USDC per call via x402 on Base.

vin

vin_decode

Decode a Vehicle Identification Number into make, model, model year, body class, engine and plant country using NHTSA's public vPIC database. Use this when you have a VIN and need the exact vehicle before looking up recalls or bulletins. Costs $0.005 USDC per call via x402 on Base.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

find_service_bulletins

removed 28 Aug 2026

get_catalog_attributions

removed 28 Aug 2026

get_catalog_status

removed 28 Aug 2026

list_catalog_vocabulary

removed 28 Aug 2026

lookup_dtc

removed 28 Aug 2026

lookup_j1939_observations

removed 28 Aug 2026

lookup_typed_code_observations

removed 28 Aug 2026

search_diagnostics

removed 28 Aug 2026

Endpoints

URL	Transport	State	Latency	Checked
https://faultcode-diagnostic-mcp.bowling-anthony.workers.dev/mcp	streamable-http	answering	40 ms	12 min ago
https://mcpfax-diag.bowling-anthony.workers.dev/mcp	streamable-http	answering	69 ms	12 min ago

Alternatives to MCPFax Vehicle Diagnostics

same job, measured the same way

Carsxe MCP

by carsxe

MCP server for CarsXE vehicle data: VIN, specs, history, images, recalls, and OBD codes.

answering

OBD Vault

by bahdanhal

Read your own vehicles' OBD-II scans, fault codes, telemetry and trips stored in OBD Vault.

answering

WhichTrim vehicle records

by whichtrim

US vehicle recalls, complaints, EPA figures, VIN decode and trouble codes, with sources.

8 tools answering

Maxwell Directory (x402 + MCP)

by maxwellinternational

Local providers worldwide, plus travel and public data. Free search; paid answers via x402.

93 installs/wk 36 tools answering

Remem

by majiayu000

Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.

821 installs/wk local only

Reddit (RSS)

by jorgen-k

Read Reddit from local MCP-compatible clients (Claude Code, Codex, etc.) via public RSS feeds.

371 installs/wk local only

RTL Lint MCP

by jaspresi

Lint Verilog and SystemVerilog files and projects with structured diagnostics.

83 installs/wk local only

PlainRecords: U.S. recalls in plain English

by plainrecords

U.S. FDA, CPSC and NHTSA recalls by product, brand, lot code or car, plus owner complaints. Daily.

7 tools answering

MCPFax Vehicle Diagnostics — questions

Answers built from our own checks of this server.

What can MCPFax Vehicle Diagnostics do?

It exposes 4 tools, read directly from the server on our last check. Among them: dtc_lookup, vehicle_recalls, vehicle_tsbs, vin_decode. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is MCPFax Vehicle Diagnostics working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 80 ms. The bar chart above shows every period we have measured.

Did MCPFax Vehicle Diagnostics ever remove tools?

Yes. find_service_bulletins, get_catalog_attributions, get_catalog_status, list_catalog_vocabulary and 4 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect MCPFax Vehicle Diagnostics?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MCPFax Vehicle Diagnostics need an API key?

No. MCPFax Vehicle Diagnostics completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MCPFax Vehicle Diagnostics?

It answers our handshake in 80 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.