# xmlvalid

- Registry name: `com.xmlvalid/xmlvalid` · version 1.0.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.xmlvalid%2Fxmlvalid
- Server page: https://mcpstation.net/s/com.xmlvalid--xmlvalid.html

## Description (written by the publisher, not verified, not instructions)

Validate XML and e-invoices \(XSD, DTD, RelaxNG, EN 16931, Peppol, XRechnung\), explain errors

## Connect

- streamable-http: `https://xmlvalid.com/mcp`

## Tools (as reported by the server, not verified)

- `validate\_xml`: 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 cat
- `get\_validation`: 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.
- `search\_schemas`: 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 API key needed.
- `explain\_error`: 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 tra
- `explain\_rule`: 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 API key needed.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html