# pyxsd (pypi · pyxsd)

Explore XML schemas, validate XML documents, and transform typed document trees.

- Trust score: 65/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `pyxsd`: 65/100 (this document), [markdown](https://verifymcp.io/servers/knorby-pyxsd/pyxsd.md), [page](https://verifymcp.io/servers/knorby-pyxsd/pyxsd)

## Channel facts

- Registry: `pypi`
- Package: `pyxsd`
- Version: `1.4.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 47/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 2 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to knorby/pyxsd).
  - Clear OSI-approved license (BSD-3-Clause).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 46/100
  - 18% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 2055 tokens (~70/item across 29 items; 15 tools + 14 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 11% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the pyxsd MCP server?

pyxsd runs locally as a PyPI package, launched with uvx --with 'pyxsd[mcp]==1.4.0' pyxsd mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add knorby-pyxsd -- uvx --with 'pyxsd[mcp]==1.4.0' pyxsd mcp
```

### Cursor

```json
{
  "mcpServers": {
    "knorby-pyxsd": {
      "command": "uvx",
      "args": [
        "--with",
        "pyxsd[mcp]==1.4.0",
        "pyxsd",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "knorby-pyxsd": {
      "command": "uvx",
      "args": [
        "--with",
        "pyxsd[mcp]==1.4.0",
        "pyxsd",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add knorby-pyxsd -- uvx --with 'pyxsd[mcp]==1.4.0' pyxsd mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "knorby-pyxsd": {
      "type": "local",
      "command": [
        "uvx",
        "--with",
        "pyxsd[mcp]==1.4.0",
        "pyxsd",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  knorby-pyxsd:
    command: "uvx"
    args: ["--with", "pyxsd[mcp]==1.4.0", "pyxsd", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "knorby-pyxsd": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "--with",
        "pyxsd[mcp]==1.4.0",
        "pyxsd",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "knorby-pyxsd": {
      "command": "uvx",
      "args": [
        "--with",
        "pyxsd[mcp]==1.4.0",
        "pyxsd",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 65, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-19 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 63, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-15 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-14 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-13 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-12 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (15)

### `pyxsd_capabilities` (~67 tokens)

Report server version, enabled tool groups, source-root, and limits.

Use this first: the reply names which tools are registered, the
configured --source-root (if any), the request/response/corpus budgets,
and whether the pydantic and arrow adapters are available.

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_inspect_schema` (~173 tokens)

Inspect a schema: overview, stubs, detail, constraints, or diagnostics.

view "overview" summarizes namespaces, roots, and counts; "compact"
and "full" describe components (depth controls how deep those views
go, not the overview); "constraints" shows value/model constraints;
"diagnostics" returns the schema compilation report and, for explicit
legacy references with prefixed substitution heads, measured
strict-namespace evidence.
roots/entry_roots values are component IDs like
"element:{namespace}name". Incomplete schemas may still be inspected
so their missing pieces can be diagnosed.

Input parameters:

- `component_ids` (array)
- `depth`
- `page`
- `schema_ref` (required)
- `view` (string)
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_find_schema_components` (~132 tokens)

Search schema components by text, name, kind, namespace, or relation.

name matches bare local names across namespaces, or Clark notation
({namespace}name) for an exact match; unknown kinds are rejected.
direction/depth walk uses/used_by relations. No matches is a valid
empty result.

Input parameters:

- `component_id`
- `depth` (integer)
- `direction` (string)
- `kind`
- `name`
- `namespace`
- `page`
- `schema_ref` (required)
- `text`
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_validate_document` (~124 tokens)

Validate one XML document, returning paged issue details.

A well-formed but schema-invalid document is a successful call with
data.valid == false; malformed XML faults with invalid_xml, missing
files fault with not_found, and a schema with unresolved
include/import dependencies faults with schema_incomplete. Omit
schema_ref to use the document's schema-location hints. Aggregate
counts come back inline; page issue details with page.next_cursor.

Input parameters:

- `document` (required)
- `page`
- `schema_ref`
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_validate_documents` (~156 tokens)

Validate many XML documents in one call, each against its own schema.

Pass one or more items; every item may carry its own optional schema_ref
(omitted falls back to document schema-location hints). The whole batch
uses one input capture and one worker request. Results keep request
order, including repeated documents. Each result is independent: a valid
document reports counts, an invalid document retains a report artifact
usable with pyxsd_explain_issue, and a per-document failure (missing
file, malformed XML, broken schema) returns a typed fault without
affecting other items. Capped by the corpus_max_files budget.

Input parameters:

- `documents` (array, required)
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_query_document` (~187 tokens)

Run XPath over a document's schema-bound projection.

Repeated nodes are identified by same-name sibling indexes in
location.path, with exact line/column locations. result "subtree"
returns that occurrence's exact original source bytes: base64 data
with its byte span and byte_length, not a serialized or regenerated
XML document, so prefixes, attribute layout, comments, and CDATA stay
as written. The element's trailing tail text is excluded, and an
occurrence whose source cannot be addressed reports a
source_unavailable fault instead of regenerated XML. Requires a
complete schema closure.

Input parameters:

- `document` (required)
- `namespaces`
- `page`
- `result` (string)
- `schema_ref` (required)
- `workspace_id` (string, required)
- `xpath` (string, required): XPath 1.0 expression; prefixes must be bound in namespaces.

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_explain_issue` (~81 tokens)

Explain a validation issue code with curated, actionable guidance.

With report and issue_index the explanation is checked against the
retained validation report: a code that disagrees with the actual
issue is rejected. Reports remain readable after workspace inputs
are released.

Input parameters:

- `code` (string, required)
- `issue_index`
- `report`

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_compare_schemas` (~222 tokens)

Diff two schemas structurally and optionally check a corpus for impact.

Identity is path-independent: byte-identical schemas at different
locations produce an empty diff, and a real edit lists the changed
components with old/new field values. Corpus documents are
classified valid/regressed/resolved/invalid, with first-issue
evidence for regressions and resolutions. Select a corpus either
explicitly or with corpus_glob; the reply reports the glob and
match count when selection was used.

Input parameters:

- `corpus` (array): Optional explicit documents validated under both schemas; count capped by the corpus_max_files budget. Mutually exclusive with corpus_glob.
- `corpus_glob`: Select corpus documents with a relative POSIX glob (* and ? within one segment, ** across segments), e.g. corpus/**/*.xml. Uploaded workspace files take precedence; an empty workspace selects from th…
- `new_schema` (required)
- `old_schema` (required)
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_inspect_model` (~150 tokens)

Project JSON Schema (optional Pydantic model) for a declaration.

element accepts the component IDs returned by schema inspection
(element:{namespace}name) or a bare local name when unambiguous;
path steps select nested declarations and use Clark names. Roots
with mixed content or repeated composites cannot be projected by
the pydantic integration; scope a path to a projectable leaf.

Input parameters:

- `element` (string, required): Root element to project: Clark notation ({namespace}name) is exact; a bare local name works when it matches exactly one global element (ambiguity lists candidates).
- `path` (array)
- `schema_ref` (required)
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_validate_data` (~88 tokens)

Validate JSON data against a projected declaration's JSON Schema.

Uses the same element/path resolution as inspect_model (Clark
notation exact, bare local names when unambiguous) and reports
structured errors for mismatched data.

Input parameters:

- `data` (required)
- `element` (string, required)
- `path` (array)
- `schema_ref` (required)
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_manage_workspace` (~72 tokens)

Create, list, or release session workspaces.

Workspaces hold uploaded inputs only; release removes those inputs
but never deletes retained artifacts. An empty workspace with a
configured --source-root captures referenced files directly from
that tree instead.

Input parameters:

- `action` (string, required)
- `workspace_id`

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_put_files` (~76 tokens)

Atomically add or replace uploaded files in a workspace.

Supplied paths are written and omitted files are retained. The
reply carries the new generation and the full merged manifest. An
empty files list is a no-op that returns the current manifest.

Input parameters:

- `files` (array, required)
- `workspace_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_list_artifacts` (~94 tokens)

List retained artifacts (reports, exports, oversized responses).

Ordered oldest-first; use envelope page.next_cursor for continuation,
including when the listing spills. An omitted limit uses the configured
page_items default when resource limits are enabled and is unlimited
otherwise. Every entry carries the id, digest, media type, size, and
local path needed for ranged reads.

Input parameters:

- `cursor`
- `limit`

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_delete_artifact` (~46 tokens)

Delete one retained artifact by id.

Destructive: the artifact's bytes are removed. Session inputs and
other artifacts are untouched.

Input parameters:

- `artifact_id` (string, required)

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

### `pyxsd_read_artifact` (~185 tokens)

Read an exact bounded byte range of a retained artifact as base64.

Returns the range plus its actual length and the artifact's total size,
digest, media type, and local path. Length can be smaller than requested
at end of file. An omitted length uses artifact_read_bytes when resource
limits are enabled and reads through EOF otherwise. Ranges that would
exceed the response budget fault with response_limit rather than
spilling into another artifact; page large reads with offset/length.
Artifacts survive workspace release.

Input parameters:

- `artifact_id` (string, required)
- `length`: Bytes to read; the base64 reply must fit the response budget, so request a smaller range instead of expecting a spill. Omit to use the configured artifact_read_bytes default, or read through EOF when…
- `offset` (integer): Byte offset into the artifact.

Output parameters:

- `artifacts` (array)
- `data`
- `page`
- `provenance` (object)
- `status` (string)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/knorby-pyxsd/pyxsd#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 61
- 2026-11-13: 76
- 2026-11-12: 61
- 2026-11-11: 60
- 2026-11-10: 60
- 2026-11-09: 59
- 2026-11-08: 59
- 2026-11-07: 58
- 2026-11-06: 58

## Common questions

### What is the pyxsd MCP server?

pyxsd is an MCP server listed in the public MCP registry as io.github.knorby/pyxsd. Explore XML schemas, validate XML documents, and transform typed document trees. This page covers its PyPI package (pyxsd).

### Is the pyxsd MCP server safe to use?

pyxsd scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 pyxsd MCP server expose?

pyxsd exposes 15 tools: pyxsd_capabilities, pyxsd_inspect_schema, pyxsd_find_schema_components, pyxsd_validate_document, pyxsd_validate_documents, and 10 more. Their descriptions and schemas cost roughly 1,853 tokens of context every time the server is loaded.

### Is the pyxsd MCP server still maintained?

pyxsd is still listed as active in the MCP registry. We last reached this channel on 21 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 pyxsd MCP server under?

pyxsd declares the BSD-3-Clause licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the pyxsd MCP server?

VerifyMCP ran 15 checks on pyxsd, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about pyxsd: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/pyxsd/
- Socket report: https://socket.dev/pypi/package/pyxsd
- Repository: https://github.com/knorby/pyxsd
- Website: https://pyxsd.knorby.com/mcp.html
- Changelog RSS feed: https://verifymcp.io/servers/knorby-pyxsd/pyxsd.xml
- Changelog JSON feed: https://verifymcp.io/servers/knorby-pyxsd/pyxsd/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/knorby-pyxsd/pyxsd.json
- HTML version of this page: https://verifymcp.io/servers/knorby-pyxsd/pyxsd
