s1000d-verify-mcp
An MCP server for evidence-based S1000D data-module verification: it checks XML validity, schema conformance, BREX rules, references, and CSDB-wide status, but does not certify S1000D conformance.
Verify a single data module/PM through well-formedness, XSD validation, BREX chain checking, and dmRef/pmRef/ICN/internalRef/applicRefId resolution, with skippable steps and capped result lists.
Validate a document against the S1000D XSD selected from
xsi:noNamespaceSchemaLocation, optionally choosing an issue.Inspect references by kind and report whether targets exist, with unresolved reasons and separate handling for S1000D specification references.
Verify all CSDB objects in folders (default DMs/PMs), page through results, and optionally write a full JSON report.
List available S1000D schema folders under
S1000D_SPEC_DIRto diagnoseschema-not-foundresults.Search extra CSDB folders, accept XML from string or path (max 5 MB), and return structured verification/error statuses.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@s1000d-verify-mcp verify data module DMC-EX-A-00-00-00-00A-040A-D_001-00_EN-US.xml"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@shuji-bonji/s1000d-verify-mcp
English | 日本語
An MCP server that lets an LLM know, with evidence, how far an S1000D® data module has been checked. It performs three steps — validation against the XML schema (XSD), a check against BREX (Business Rules Exchange), and resolution of references (dmRef, pmRef, ICN, internalRef and applicRefId) — and returns the results combined into a single verification status (verification). This verification status has the same shape as the one s1000d-reader-mcp embeds in its content responses.
This is a personal project and is not affiliated with ASD (Aerospace, Security and Defence Industries Association of Europe). S1000D® is a registered trademark of ASD.
The S1000D specification, XML schemas, default BREX and official samples are not included in any package or repository, because their terms of use do not grant redistribution. To run XSD validation and checks against the default BREX, obtain them froms1000d.org yourself and point the S1000D_SPEC_DIR environment variable at the extracted folder.
What it does
Tool | Description |
| Validates one data module in the order well-formedness → XSD → BREX chain → references, and returns |
| Runs XSD validation only. The XSD to use is chosen from the file name in |
| Collects references of 5 kinds ( |
| Validates the CSDB objects in a folder (DMC and PMC by default) in one run, and returns the verification status of each object and a count summary. Read the results in parts with |
| Runs the same verification as |
| Reconciles a data module list (DML) or a data dispatch note (DDN) with the CSDB. For each DML entry ( |
| Returns the list of |
Verification status (verification)
Field | Value | Meaning |
|
| XSD found and validated with 0 violations / violations found / XSD not found (reason in |
|
| 0 violations in every layer / violations found / an unresolved BREX or a rule that cannot be evaluated / skipped |
|
| 0 unresolved / unresolved references found / skipped |
schema-not-found is not valid. It means that XSD validation did not run.
Related MCP server: S1000D MCP Server
What it does not do
It does not decide conformance to S1000D.
schema: validandbrex: passedmean only that no errors were found against the XSD and the BREX rules that a machine can check.nonContextRules(agreements written as prose) are returned asmanualChecks, and a person makes the judgement. A project's business rules document is outside the scope of every tool.It does not return explanations of BREX rules or the meaning of values. That is the job of
explain_brex/lookup_valueins1000d-brex-mcp. Severity level codes (brsl01tobrsl99) are returned as they are.It does not evaluate applicability (which product the content applies to).
check_referencesonly looks at whether the target ofapplicRefIdexists. The evaluation is done bys1000d-reader-mcp. The exception issuggest_fixeswithproduct, which reports only applicability that cannot be decided because the product lacks a value.It does not apply fixes to the document.
suggest_fixesonly returns candidates. Have the LLM choose among the candidates, and ask the user whenconfidenceisnone(theinstructionssay the same).It does not interpret DML values (
dmlType/dmlEntryType/issueType).reconcile_dmlcompares identifiers and issues only; it does not verify the content of the listed objects (useverify_csdbfor that).
In a document that violates the XSD, elements may be in positions that differ from the specification, so BREX violations can be reported falsely or hidden. Whenschema.state is invalid, read the BREX results as a rough indication only (the response also says so in _notes).
Configuration
Environment variable | Description |
| The folder where you extracted the S1000D distribution you obtained. The XSDs ( |
| The folder that holds the project's data modules. Several folders can be given, separated by |
Folders can also be given with the tool argument csdbDirs. When the argument is given, only those folders are used; S1000D_CSDB_DIR and csdbDirs in the config file are not used (they are not added together). Folders that do not exist are skipped and listed in _notes of the response. When none is left, the tool returns no-csdb (below).
Errors
An error that the caller can fix by changing an argument is not returned as a tool failure (isError) but in the same shape as s1000d-writer-mcp.
{ "error": { "code": "file-not-found", "path": "/path", "detail": "File not found: /path/to/DMC-….XML" } }
| Meaning |
| There is no file at the path given in the argument |
| No CSDB folder exists (pass |
| An argument is malformed, or a required argument is missing |
path names the argument to fix (/path, /csdbDirs and so on), not a file path.
Config file (when environment variables are not passed, as with plugins in Claude Desktop)
If S1000D_SPEC_DIR / S1000D_CSDB_DIR are not set, the server reads the config file ~/.config/s1000d-stack/config.json (under XDG_CONFIG_HOME if it is set; S1000D_CONFIG changes the location). Claude Desktop does not pass environment variables to servers installed as plugins, and does not substitute ${VAR} written in the plugin's env. When you install the server as a plugin, write the folders here.
{
"specDir": "/path/to/s1000d/issue-7",
"csdbDirs": ["/path/to/your/csdb"]
}Environment variables take precedence when they are set. Paths that start with ~/ are accepted. The config file is read again on every call, so the server does not need to be restarted after you edit it.
Configuration example for Claude Desktop / Claude Code
{
"mcpServers": {
"s1000d-verify": {
"command": "npx",
"args": ["-y", "@shuji-bonji/s1000d-verify-mcp"],
"env": {
"S1000D_SPEC_DIR": "/path/to/s1000d/issue-7",
"S1000D_CSDB_DIR": "/path/to/your/csdb"
}
}
}
}Running over HTTP (embedding in a product)
The default is stdio. With --http the server starts over Streamable HTTP, so a CSDB product's server or a web application can call it over HTTP (the embedding foundation of stage 2.5).
npx -y @shuji-bonji/s1000d-verify-mcp --http # http://127.0.0.1:3000/mcp
npx -y @shuji-bonji/s1000d-verify-mcp --http --port 3102 --path /verifyArgument | Default | Meaning |
|
| Address to bind to |
|
| Port; |
|
| Path of the MCP endpoint. |
| (see below) | Host names allowed in the |
| (see below) | Host names allowed in the |
When --host is a loopback address (127.0.0.1 / ::1 / localhost), Host and Origin are limited to localhost names (DNS rebinding protection). When bound to any other address they are not checked, so put the server behind the product's reverse proxy or authentication. Authentication, authorization and multi-tenancy are not part of this server. Environment variables and the config file work the same as with stdio.
How it works
All validation logic lives in the shared library @shuji-bonji/s1000d-core; this server holds only the interpretation of arguments and the shape of the responses. XSD validation uses libxml2-wasm (the WebAssembly build of libxml2), and each XSD is compiled once and reused, so the 106 official samples of Issue 7 are validated in under 0.5 seconds. The BREX check calls the same functions as s1000d-brex-mcp, so the results of the two servers match.
Development
npm install
npm test # runs with self-made test data only
npm run test:spec # uses the distribution you obtained (set the location with S1000D_SPEC_DIR; default ../../specs/s1000d/issue-7)
npm run build && S1000D_SPEC_DIR=/path/to/issue-7 npm start # starts over stdioLicense
MIT. S1000D® is a registered trademark of ASD. This software is not affiliated with ASD and does not include the specification, schemas or official samples.
Available Tools
5 toolscheck_referencesA
List the references of one document and whether each target exists: dmRef (all contexts: brexDmRef, applicCrossRefTableRef, pmEntry, body), pmRef, ICN (graphic/@infoEntityIdent via the DOCTYPE ENTITY declaration to a file), internalRef (ids in the same document) and applicRefId (applic ids or referencedApplicGroupRef/applicRef). Unresolved references carry a reason (not-found, no-entity-declaration, file-not-found, no-such-id, no-csdb). dmRef to modelIdentCode "S1000D" point to the specification itself and are listed separately.
Inputs: xml, path, kinds, csdbDirs, +2 more.
list_schemasA
Show which S1000D XML schema folders (xml_schema_flat/ containing brex.xsd) were found under S1000D_SPEC_DIR, with the issue read from brex.xsd and the schema names available. Use it to diagnose schema-not-found results.
Inputs: no named parameters.
validate_schemaA
Validate one document against the S1000D XML schema (XSD) named by its xsi:noNamespaceSchemaLocation. The XSD is taken from the xml_schema_flat/ folder found under S1000D_SPEC_DIR (the issue is read from brex.xsd there). Errors are libxml2 messages with line/column. Returns schema-not-found with a reason when no suitable XSD is available.
Inputs: xml, path, issue, maxErrors.
verify_csdbA
Verify every CSDB object (data modules by default; optionally publication modules etc.) found in the given folders, and return one VerificationStatus per object plus totals (valid / XSD errors / BREX violations / unresolved references / unreadable). Use offset/limit to page. Pass reportPath to also write the full JSON report to a file.
Inputs: skip, limit, offset, include, +2 more.
verify_data_moduleA
Verify one S1000D data module: well-formedness, XML schema (XSD) validation against the user's own S1000D schemas (S1000D_SPEC_DIR), BREX checks along the brexDmRef chain, and reference resolution (dmRef, pmRef, ICN entities, internalRef, applicRefId). Returns a "verification" status (the same VerificationStatus that s1000d-reader-mcp embeds) plus the details of each step. Does NOT decide S1000D conformance.
Inputs: xml, path, skip, csdbDirs, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
The tools mostly have distinct roles: schema listing, single-document schema validation, full data-module verification, bulk CSDB verification, and reference checking. However, reference resolution is both a step inside verify_data_module and the explicit purpose of check_references, and verify_csdb overlaps in aggregate with verify_data_module, so boundaries are clear but not perfect.
All tool names use a consistent snake_case verb_noun pattern: validate_schema, verify_csdb, list_schemas, verify_data_module, and check_references. The verbs are varied but predictable and each name clearly identifies its object.
Five tools is well-scoped for a focused S1000D verification server. Each tool earns its place by covering schema discovery, validation, single-object verification, bulk verification, and reference diagnostics.
The surface covers the core verification lifecycle: schema discovery, XSD validation, single and bulk S1000D verification including BREX and references, plus reference diagnosis. Minor gaps include no standalone BREX-only or publication-module-specific verification tool, though verify_csdb and verify_data_module cover much of that indirectly.
Maintenance
Related MCP Connectors
Check ISO 20022 messages (pacs.008, pain.001, camt.053, seev.031) against schema and rules.
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.
Check AI work against requirements and return structured verdicts, findings, and repair steps.
Manage SysML2 projects; check, evaluate, verify, query, document and diagram models.
Related MCP Servers
- AlicenseAqualityCmaintenanceChecks documents against international standards (e.g., ICAO, Hague-Visby) to verify internal consistency and completeness, returning a machine-readable verdict for agent decision-making.258 npmMIT
- AlicenseAqualityBmaintenanceProvides LLM agents with a toolset for reviewing S1000D technical publications, including XML schema validation, cross-reference and applicability checks, skeleton generation, and AI-suggested fixes.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables language models to query, inspect, check, and validate XML documents through XPath 1.0 expressions and XSD schemas without loading the full document into a context window. Documents stay on disk while models retrieve exact counts, values, and structural summaries via tool calls.1Apache 2.0
- AlicenseAqualityCmaintenanceEnables validating IFC models against IDS requirements with coverage reporting, auditing LOD by project stage, and extracting quantity take-offs, including combined audit summaries and full BIM health checks. It exposes these capabilities as MCP tools for Claude Desktop, producing Excel, HTML, and BCF reports.5MIT