# JDM Factory Service Manuals (remote · jdmfsm.info)

2,000+ factory service manuals for Japanese cars and Jeep: DTCs, repair pages, wiring diagrams.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `jdmfsm.info`: 72/100 (this document), [markdown](https://verifymcp.io/servers/balexandrov-jdmfsm/jdmfsm.md), [page](https://verifymcp.io/servers/balexandrov-jdmfsm/jdmfsm)

## Channel facts

- Endpoint: `https://jdmfsm.info/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1481 tokens (~246/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the JDM Factory Service Manuals MCP server?

JDM Factory Service Manuals is a hosted endpoint at https://jdmfsm.info/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http balexandrov-jdmfsm 'https://jdmfsm.info/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "balexandrov-jdmfsm": {
      "url": "https://jdmfsm.info/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "balexandrov-jdmfsm": {
      "type": "http",
      "url": "https://jdmfsm.info/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.balexandrov-jdmfsm]
url = "https://jdmfsm.info/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "balexandrov-jdmfsm": {
      "type": "remote",
      "url": "https://jdmfsm.info/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add balexandrov-jdmfsm --url 'https://jdmfsm.info/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  balexandrov-jdmfsm:
    url: "https://jdmfsm.info/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "balexandrov-jdmfsm": {
      "Transport": "http",
      "Url": "https://jdmfsm.info/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add balexandrov-jdmfsm -t streamable-http -u 'https://jdmfsm.info/mcp'
```

### Other

```json
{
  "mcpServers": {
    "balexandrov-jdmfsm": {
      "type": "http",
      "url": "https://jdmfsm.info/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 70, +1)

- [security] Tool “page_image” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads

### 2026-11-15 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 69)

First indexed and scored.

## MCP tools (6)

### `find_manuals` (~377 tokens)

Find manuals

Find the service manual for a car. Accepts how people describe it: brand, model name, year,
chassis code, engine or transmission code, e.g. "2004 Sentra 1.8", "B15", "QG18DE", "Mazda 3".
Returns manuals best match first, factory service manuals before owner's manuals; pass a
result's 'manual' to search / lookup_dtc / get_contents. A manual is one book: 'title', 'type'
(service, wiring, body, owners, features, parts, bulletins, accessory, brochure, article,
aftermarket; '' if
unknown), 'format' (pdf / html) and 'lang' say which; only English books are searchable. A year
folder's books share the folder: pass the folder ("Japan/Subaru/Forester/2008") as 'manual' to
search them all. A result with a 'file' is one book among
the loose files of a model folder: read it with read_pages(file, page) or
get_contents(manual, file); search and lookup_dtc on its 'manual' cover that whole folder.
A 17-character VIN or a Japanese frame number ("JZX100-0012345") is read as make, chassis code and
year; the results then say how under 'read_as'. An engine or transmission code finds the books that
print it, also written short or without hyphens ("k24" -> K24A3, "1jzgte" -> 1JZ-GTE); 'read_as' then
says what it is ("K24: Honda engine (K24A1, K24A3 ...)").

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (array)

### `get_contents` (~70 tokens)

Table of contents

List the files (sections) of a manual with what each covers, page counts and links.
With 'file' (its full path, or its name within 'manual'), list that file's bookmarks (its own
table of contents) instead.

Input parameters:

- `file`
- `manual` (string, required)

### `search` (~324 tokens)

Search a manual

Look up components, systems and jobs in one car's manual index, e.g. "timing chain",
"camshaft position sensor", "a/t fluid", "spark plug", "brake caliper". 'manual' is required:
a manual from find_manuals, or its model folder to cover all years. The query is split into the
manual's index terms; pages holding all of them come first, and pages where a bookmark names a
term (where the manual's own index would point) rank above passing mentions. An abbreviation the
manual doesn't use is read as the term it does ("bsm" -> "blind spot"), and "timing" alone (or "timing
diagram", "timing marks") as the timing chain/belt job, both shown under 'read_as'. A word for the
kind of page beside the part ("fuel pump wiring diagram", "... connector", "... specifications") ranks the
part's pages headed that way first (shown under 'page_kind'). Words not in the
index are listed under 'not_indexed' with index terms that start the same way; an engine code the
manual doesn't cover (engine, transmission, chassis or model) is listed under 'not_here' with the codes
of that kind the manual does cover and the model folders whose manuals print it. Only English text is
indexed; a book in another language is listed by get_contents and read_pages reads it.

Input parameters:

- `limit` (integer)
- `manual` (string, required)
- `query` (string, required)

### `lookup_dtc` (~150 tokens)

Look up a trouble code

Look up a diagnostic trouble code (P0340, C1105, U1000, or an old Nissan blink code like 34)
in one car's manual and return where its diagnosis starts: page, title, and the parent bookmarks
('within'). A manual covering several engines or systems has one diagnosis per variant, so check
'within' (e.g. "QG18DE" vs "QR25DE") against the car. 'manual' is required: a manual from
find_manuals, or its model folder to cover all years (listed newest year first).

Input parameters:

- `code` (string, required)
- `limit` (integer)
- `manual` (string, required)

Output parameters:

- `result` (array)

### `read_pages` (~55 tokens)

Read pages

Read the text of 'count' pages (max 6) of a file, starting at 'page' (1-based).

Input parameters:

- `count` (integer)
- `file` (string, required)
- `page` (integer, required)

Output parameters:

- `result` (array)

### `page_image` (~184 tokens)

Page image

Render one PDF page as a PNG image: use it for wiring diagrams, connector pin views,
exploded views and tables that read poorly as text. Returns a short text part first (the page
link, its heading and text) and then the image. If no image reaches you, your client does not
pass images on: use the text, and give the user the link to see the page; asking again will not help.
If the image arrives as a file attachment instead (ChatGPT), show the user the page by embedding
that attached file in your answer, then give the link.
format="pdf" returns the page as a one-page PDF instead of the image (for clients that read PDFs
but not images).

Input parameters:

- `file` (string, required)
- `format` (string)
- `page` (integer, required)
- `zoom` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/balexandrov-jdmfsm/jdmfsm#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70
- 2026-11-15: 69
- 2026-11-14: 69

## Common questions

### What is the JDM Factory Service Manuals MCP server?

JDM Factory Service Manuals is an MCP server listed in the public MCP registry as io.github.balexandrov/jdmfsm. 2,000+ factory service manuals for Japanese cars and Jeep: DTCs, repair pages, wiring diagrams. This page covers its hosted endpoint (https://jdmfsm.info/mcp).

### Is the JDM Factory Service Manuals MCP server safe to use?

JDM Factory Service Manuals scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the JDM Factory Service Manuals MCP server expose?

JDM Factory Service Manuals exposes 6 tools: find_manuals, get_contents, search, lookup_dtc, read_pages, page_image. Their descriptions and schemas cost roughly 1,160 tokens of context every time the server is loaded.

### Does the JDM Factory Service Manuals MCP server require authentication?

No. We connected to JDM Factory Service Manuals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the JDM Factory Service Manuals MCP server still maintained?

JDM Factory Service Manuals is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the JDM Factory Service Manuals MCP server?

VerifyMCP ran 13 checks on JDM Factory Service Manuals, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://jdmfsm.info/mcp
- Repository: https://github.com/balexandrov/jdmfsm-mcp
- Website: https://jdmfsm.info/Auto/mcp.html
- Changelog RSS feed: https://verifymcp.io/servers/balexandrov-jdmfsm/jdmfsm.xml
- Changelog JSON feed: https://verifymcp.io/servers/balexandrov-jdmfsm/jdmfsm/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/balexandrov-jdmfsm/jdmfsm.json
- HTML version of this page: https://verifymcp.io/servers/balexandrov-jdmfsm/jdmfsm
