Remote xmlvalid server that lets an assistant validate XML documents and e-invoices against schemas and business rules, and explain validation errors.
What you can do
Validate XML documents for well-formedness and against XSD, DTD or RelaxNG schemas, or e-invoice Schematron rules (EN 16931, Peppol BIS, XRechnung, Factur-X, national formats), from pasted text or a public URL
Check the status and result of a validation that was still queued or running when it returned
Search the catalog of official schemas by name, namespace, root element or area to get the slug, version and rules a schema checks
Explain XML parsing and schema validation error messages from libxml2, Java Xerces and .NET, with cause and fix
Explain e-invoicing business rules by id, including message, level, rule sets and how to fix failing invoices
When to use it
Useful when you work with XML feeds, invoices or integrations and want an assistant to check documents against official schemas and e-invoice rule sets, or to make sense of cryptic validator error messages without leaving the conversation.
Requirements
A remote endpoint at xmlvalid.com over streamable HTTP; no local install. An xmlvalid API key sent in the Authorization header is needed for validate_xml and get_validation; the schema search and explanation tools work without a key.
Before you install
The API key is a secret sent in the Authorization header, so keep it out of shared logs. Documents passed by URL are fetched by the third-party service, and submitted XML content leaves your machine for validation. Validation results are only kept for 24 hours.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.xmlvalid%2Fxmlvalid/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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 key's monthly quota.
Parametersurlxmlnamewaitschemarules_version
get_validation
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.
Parametersidrequired
search_schemas
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.
Parametersquery
explain_error
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 trace prefix included. No API key needed.
Parametersmessagerequired
explain_rule
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.
Parametersidrequired
Version history
1
v1.0.0LatestOct 22, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.