JDM Factory Service Manuals
REMOTE · JDMFSM.INFO
2,000+ factory service manuals for Japanese cars and Jeep: DTCs, repair pages, wiring diagrams.
Available components
Last scanned (18 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +1
- 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 security
- 15 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://jdmfsm.info/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jdmfsm.info | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 43f671d005a5de260e55e9bb64b5cea0 |
| SANs: jdmfsm.info, ipn.jdmfsm.info, *.ipn.jdmfsm.info | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of jdmfsm.info. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| info. | DS published | 9986 | 8 | Verified |
| jdmfsm.info. | DS published | 2371 | 13 | Verified |
| jdmfsm.info. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=2592000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jdmfsm.info/mcp | Verified | 200 | |
| http (plaintext) | http://jdmfsm.info/mcp | HTTPS enforced | 301 | https://jdmfsm.info/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_manuals Find manuals ~377
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 ...)").
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_contents Table of contents ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | – | – | – |
| manual | string | yes | – |
No output schema declared.
No examples provided.
lookup_dtc Look up a trouble code ~150
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).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| limit | integer | – | – |
| manual | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
page_image Page image ~184
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).
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
| format | string | – | – |
| page | integer | yes | – |
| zoom | number | – | – |
No output schema declared.
No examples provided.
read_pages Read pages ~55
Read the text of 'count' pages (max 6) of a file, starting at 'page' (1-based).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| file | string | yes | – |
| page | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search Search a manual ~324
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| manual | string | yes | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · jdmfsm.info
claude mcp add --transport http balexandrov-jdmfsm 'https://jdmfsm.info/mcp'
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.