Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

pyxsd

PYPI · PYXSD

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

Available components

+4 this week 65 Trust /100

Last scanned (11 hours ago)

Scores higher than 57% of PyPI servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security47
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 2 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to knorby/pyxsd). View diagnostics → Pass
  • Clear OSI-approved license (BSD-3-Clause).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability46
  • 18% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2055 tokens (~70/item across 29 items; 15 tools + 14 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 11% of tool parameters carry a description.Partial
  • 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

Diagnostics

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 21 Nov 2026 · Analysed pypi/pyxsd@1.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo knorby/pyxsd
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/knorby/pyxsd/.github/workflows/release.yml@refs/tags/v1.4.0
Rekor log index 3752897597
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:538b05fbdcca51fc5c59fc51626d7828546162945c7d885b1648a05c7f5b89ab

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 2 packages
Packages resolved 2
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~1,853 tokens

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 →

Tool Tokens
pyxsd_capabilities ~67

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_compare_schemas ~222

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.

NameTypeReqDescription
corpusarray–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–yes–
old_schema–yes–
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_delete_artifact ~46

Delete one retained artifact by id. Destructive: the artifact's bytes are removed. Session inputs and other artifacts are untouched.

NameTypeReqDescription
artifact_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_explain_issue ~81

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.

NameTypeReqDescription
codestringyes–
issue_index–––
report–––
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_find_schema_components ~132

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.

NameTypeReqDescription
component_id–––
depthinteger––
directionstring––
kind–––
name–––
namespace–––
page–––
schema_ref–yes–
text–––
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_inspect_model ~150

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.

NameTypeReqDescription
elementstringyesRoot element to project: Clark notation ({namespace}name) is exact; a bare local name works when it matches exactly one global element (ambiguity lists candidates).
patharray––
schema_ref–yes–
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_inspect_schema ~173

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.

NameTypeReqDescription
component_idsarray––
depth–––
page–––
schema_ref–yes–
viewstring––
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_list_artifacts ~94

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.

NameTypeReqDescription
cursor–––
limit–––
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_manage_workspace ~72

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.

NameTypeReqDescription
actionstringyes–
workspace_id–––
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_put_files ~76

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.

NameTypeReqDescription
filesarrayyes–
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_query_document ~187

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.

NameTypeReqDescription
document–yes–
namespaces–––
page–––
resultstring––
schema_ref–yes–
workspace_idstringyes–
xpathstringyesXPath 1.0 expression; prefixes must be bound in namespaces.
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_read_artifact ~185

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.

NameTypeReqDescription
artifact_idstringyes–
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…
offsetinteger–Byte offset into the artifact.
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_validate_data ~88

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.

NameTypeReqDescription
data–yes–
elementstringyes–
patharray––
schema_ref–yes–
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_validate_document ~124

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.

NameTypeReqDescription
document–yes–
page–––
schema_ref–––
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

pyxsd_validate_documents ~156

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.

NameTypeReqDescription
documentsarrayyes–
workspace_idstringyes–
NameTypeReqDescription
artifactsarray––
data–––
page–––
provenanceobject––
statusstring––
warningsarray––

No examples provided.

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.

pypi · pyxsd

# add to Claude Code
claude mcp add knorby-pyxsd -- uvx --with 'pyxsd[mcp]==1.4.0' pyxsd mcp
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.