oxml-mcp
OCI · GHCR.IO/SEBASTIENROUSSEAU/OXML-MCP
XML tools for agents: XPath queries, inspection, and schema validation in Rust.
Available components
Last scanned (1 hour ago)
Scores higher than 93% of OCI servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT OR Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 466 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: 0.90 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.0.13 → 0.0.15 functional
- Package version: 0.0.13 → 0.0.14 functional
- 31 Oct 26 0
- Package version: 0.0.11 → 0.0.13 functional
- Package version: 0.0.11 → 0.0.12 functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/sebastienrousseau/oxml-mcp@0.0.15
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
xml_check ~38
Check whether a document is well-formed, and report the line and column if it is not.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XML document |
| Name | Type | Req | Description |
|---|---|---|---|
| nodes | integer | yes | How many nodes the document has. |
| well_formed | boolean | yes | Always true: a document that is not well-formed is an error, not a result. |
No examples provided.
xml_format ~134
Format an XML document with configurable indentation (spaces) and empty element style, or minify it. Use this to pretty-print or compact XML.
| Name | Type | Req | Description |
|---|---|---|---|
| empty_elements | string|null | – | Empty element style: 'self-closing' (`<a/>`), 'spaced' (`<a />`), or 'expanded' (`<a></a>`). Default is 'self-closing'. |
| indent | integer|null | – | Spaces per indentation level (e.g. 2 or 4). Set to 0 or omit to minify without extra whitespace. |
| xml | string | yes | The XML document |
| Name | Type | Req | Description |
|---|---|---|---|
| formatted_size | integer | yes | Formatted size of the XML in bytes. |
| original_size | integer | yes | Original size of the XML in bytes. |
| xml | string | yes | The formatted XML. |
No examples provided.
xml_inspect ~55
Summarise a document's structure: element counts, depth, the element names present, and the namespaces it uses. Use this to understand a document's shape before querying it.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XML document |
| Name | Type | Req | Description |
|---|---|---|---|
| elements | object | yes | Every element name present, with how many times it occurs. |
| max_depth | integer | yes | The deepest element, counting the root as 1. |
| namespaces | object | yes | Every namespace URI in use, with how many elements are in it. |
| root | string | yes | The local name of the root element, or `none`. |
No examples provided.
xml_query ~122
Evaluate an XPath 1.0 expression against an XML document and return the matching values. Use this instead of reading a large document into context.
| Name | Type | Req | Description |
|---|---|---|---|
| namespaces | object | – | Namespace prefixes used in the expression, mapping prefix to URI, e.g. {"m": "urn:example"}. A prefix must be bound here; it is not read from the document. Call xml_inspect to see which namespaces a… |
| xml | string | yes | The XML document |
| xpath | string | yes | An XPath 1.0 expression |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many nodes matched. A scalar expression counts as one. |
| values | array | yes | The matched values in document order, empty text omitted. A scalar expression -- a number, string or boolean -- is one value. |
No examples provided.
xml_validate ~53
Validate an XML document against an XML Schema (XSD). Returns every violation with the path to the element it concerns.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XML document |
| xsd | string | yes | The XML Schema |
| Name | Type | Req | Description |
|---|---|---|---|
| valid | boolean | yes | Whether the document conforms to the schema. |
| violations | array | yes | Every violation found; empty when the document is valid. |
No examples provided.
How do I install the oxml-mcp server?
oxml-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/sebastienrousseau/oxml-mcp:0.0.15. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/sebastienrousseau/oxml-mcp
claude mcp add sebastienrousseau-oxml-mcp -- docker run --rm -i ghcr.io/sebastienrousseau/oxml-mcp:0.0.15
What is the oxml-mcp server?
oxml-mcp is listed in the public MCP registry as io.github.sebastienrousseau/oxml-mcp. XML tools for agents: XPath queries, inspection, and schema validation in Rust. This page covers its container image (ghcr.io/sebastienrousseau/oxml-mcp).
Is the oxml-mcp server safe to use?
oxml-mcp scores 55 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the oxml-mcp server expose?
oxml-mcp exposes 5 tools: xml_check, xml_format, xml_inspect, xml_query, xml_validate. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Is the oxml-mcp server still maintained?
oxml-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the oxml-mcp server under?
oxml-mcp declares the MIT OR Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.