xmlvalid
Server Details
Validate XML and e-invoices (XSD, DTD, RelaxNG, EN 16931, Peppol, XRechnung), explain errors
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- xmlvalid
TDQS
Scored across 5 tools
validate_xml (start a job) versus get_validation (poll a job) and explain_error (parse a message) versus explain_rule (look up a rule id) are each defined by distinct inputs, so misselection risk is low. The only soft overlap is between explain_error and explain_rule when an error message cites a rule id, but the descriptions make the boundary clear enough.
All five names follow a clean verb_noun snake_case pattern: explain_error, explain_rule, get_validation, search_schemas, validate_xml. Verbs are varied but chosen to match the action rather than randomly, which keeps the convention predictable.
Five tools is tightly scoped to the domain: discover a schema, run a validation, poll its result, and explain the two kinds of failure output. Each tool maps to a distinct step in the validation workflow with no filler.
The lifecycle is covered end to end, including async polling via get_validation and troubleshooting via the two explain tools. The notable gap is saved schemas: validate_xml accepts "@orders-v3" style references but no tool lets an agent list, save, or inspect them, and there is no cancel operation for runaway jobs.
Available Tools
5 toolsexplain_errorExplain an XML errorARead-onlyIdempotentInspect
Explain an XML parsing or schema validation error message: what it means, why it happens and how to fix it, with an example. Understands libxml2 (xmllint, PHP, Python lxml, xmlvalid), Java (Xerces cvc-* codes, SAXParseException) and .NET (System.Xml) wording; paste the message as reported, stack trace prefix included. No sign-in or API key needed.
Inputs: message (required).
explain_ruleExplain a business ruleARead-onlyIdempotentInspect
Explain an e-invoicing business rule by its id, such as BR-CO-15, BR-DE-1, PEPPOL-EN16931-R001 or a national CIUS rule: its message, level, the rule sets it belongs to, why invoices fail it and how to fix them. No sign-in or API key needed.
Inputs: id (required).
get_validationGet a validation resultARead-onlyIdempotentInspect
The status and result of a validation started with validate_xml that was still running when it returned (status "queued" or "running"). Results are kept for 24 hours.
Inputs: id (required). Returns: id, error, rules, result, +7 more
search_schemasSearch XML schemasARead-onlyIdempotentInspect
Search xmlvalid's catalog of official XML schemas (UBL, CII, Peppol, XRechnung, Factur-X, ISO 20022, HL7, sitemaps…) by name, namespace, root element or area. Returns each schema's slug to pass to validate_xml, its version and the business rules it checks. No sign-in or API key needed.
Inputs: query. Returns: shown, total, schemas
validate_xmlValidate XMLAInspect
Validate an XML document with xmlvalid: well-formedness, an XSD, DTD or RelaxNG schema, and for e-invoices the Schematron business rules of EN 16931, Peppol BIS, XRechnung, Factur-X and national formats. Pass the document as xml (its text) or url (a public http(s) address), and a schema: a catalog slug from search_schemas, a saved schema ("@orders-v3"), or "auto" to use the e-invoice profile the document names. Without a schema only well-formedness is checked. Returns valid, errors and warnings with line, column, message, rule and a help_url explaining each. Counts as one API validation of the account's monthly quota.
Inputs: url, xml, name, wait, +2 more. Returns: id, error, rules, result, +7 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair
Validiert E-Rechnungen (ZUGFeRD/Factur-X, XRechnung) gegen EN 16931 mit Korrekturvorschlägen.
XRechnung/ZUGFeRD erstellen, gegen EN 16931 prüfen, Fehler mit Regel-ID erklären. Ohne Konto.
Validate, parse and render EU e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS 3.0, KSeF.
Related MCP Servers
- AlicenseAqualityBmaintenanceValidates electronic invoices (XRechnung, ZUGFeRD, Factur-X, Peppol BIS, etc.) against authority-pinned rules and explains failures.2247 npmMIT
- AlicenseAqualityDmaintenanceValidates EU electronic invoices (Peppol, XRechnung, FatturaPA, etc.) and explains validation error codes, enabling AI coding agents to check invoice validity and get fixes before rejection.346 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to detect, parse, validate, and render European e-invoices such as XRechnung, ZUGFeRD, Factur-X, Peppol BIS Billing 3.0, EN 16931 UBL/CII, and Polish KSeF FA(3) using official rule sets. It is a remote, stateless Streamable HTTP server with tools for invoice inspection, compliance validation, and HTML/PDF rendering.MIT
- AlicenseNot gradedqualityDmaintenanceEU e-invoice validation, as a developer API. Check whether an electronic invoice conforms to EN 16931 — the European standard behind France, Germany, Belgium, Poland and the 2030 ViDA mandate — with a single REST call. Structured JSON errors mapped to the official BR-* business rules. No enterprise sales call required.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.