xmlvalid MCP server
com.xmlvalid/xmlvalidxmlvalid.comstreamable-httpv1.0.0Scanned
Validate XML and e-invoices (XSD, DTD, RelaxNG, EN 16931, Peppol, XRechnung), explain errors
5 tools: 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the xmlvalid MCP server can do
The xmlvalid MCP server is published by xmlvalid.com, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (validate_xml); 1 tool can send data out of your system (validate_xml).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
explain_errorExplain an XML parsing or schema validation error message: what it means, why it happens and how to fix it, with an example.No findings
Why it is in this group
- The name "explain_error" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain Error
- readOnlyHint: true
explain_ruleExplain 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 invoice…No findings
Why it is in this group
- The name "explain_rule" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain Rule
- readOnlyHint: true
get_validationThe status and result of a validation started with validate_xml that was still running when it returned (status "queued" or "running").No findings
Why it is in this group
- The name "get_validation" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get Validation
- readOnlyHint: true
search_schemasSearch xmlvalid's catalog of official XML schemas (UBL, CII, Peppol, XRechnung, Factur-X, ISO 20022, HL7, sitemaps…) by name, namespace, root element or area.No findings
Why it is in this group
- The name "search_schemas" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search Schemas
- readOnlyHint: true
validate_xmlValidate 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-…Reads text others writeCan send data outNo findings
Why it is in this group
- The name "validate_xml" says "validate": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: Validate Xml
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://xmlvalid.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://xmlvalid.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://xmlvalid.com/mcp: tools/list returned 5 tools to an anonymous client, including validate_xml (write)
Posture changes
- Nov 14, 2026
- Tools that change things, listed without credentials: 0 to 1
- RFC 9728 protected resource metadata: none to https://xmlvalid.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://xmlvalid.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1; RFC 9728 protected resource metadata: none -> https://xmlvalid.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://xmlval…View diff
- Tools that change things, listed without credentials: 0 to 1
- RFC 9728 protected resource metadata: none to https://xmlvalid.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://xmlvalid.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http xmlvalid https://xmlvalid.com/mcpclaude mcp add --transport http xmlvalid https://xmlvalid.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__xmlvalid__get_validation",
"mcp__xmlvalid__search_schemas",
"mcp__xmlvalid__explain_error",
"mcp__xmlvalid__explain_rule"
],
"ask": [
"mcp__xmlvalid__validate_xml"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as xmlvalid. Review it before you use it.
Capability tags behind 1 rule
- mcp__xmlvalid__validate_xml untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.xmlvalid/xmlvalid/verify?hash=f1f63c346bc3d01be2987aaf64723502c28bea75189fbdcf5fe6a512187b9b75" | jq -e '.changed == false'Pinned hash f1f63c346bc3, from Nov 8, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.xmlvalid/xmlvalid/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.xmlvalid/xmlvalid)Source: MCP Registry. Synced Oct 22, 2026, 22:17 UTC.
xmlvalid MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the xmlvalid MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the xmlvalid MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the xmlvalid MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the xmlvalid MCP server have?
- 5 tools: 5 read. validate_xml, get_validation, search_schemas, explain_error and explain_rule.
Does the xmlvalid MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the xmlvalid MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): validate_xml.
Has the xmlvalid MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.