io.github.SemanticDataCharter/sdcvalidator
PYPI · SDCVALIDATOR
SDC4 structural validator with ExceptionalValue recovery; thin wrapper over xmlschema.
Available components
Last scanned (6 hours ago)
Scores higher than 89% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 2 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SemanticDataCharter/sdcvalidator). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 270 tokens (~90/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 4.6.1 → 4.6.3 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 +1
- Malware scan: unverified → pass ▲ security
- Package version: 4.6.0 → 4.6.1 functional
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 pypi/sdcvalidator@4.6.3
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 | SemanticDataCharter/sdcvalidator |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SemanticDataCharter/sdcvalidator/.github/workflows/release.yml@refs/tags/v4.6.3 |
| Rekor log index | 3614507804 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d735525a33c7d36b342649c072b938de5921bf1f70835b5261fcf9c320b83714 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_schema_compliance ~53
Check if an XSD schema follows SDC4 principles (no xsd:extension, restriction only). Does not validate instances.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_path | string | yes | Path to the XSD schema file to check. |
No output schema declared.
No examples provided.
validate_and_report ~83
Validate an XML instance and return a detailed report with two-tier error classification (structural vs semantic).
| Name | Type | Req | Description |
|---|---|---|---|
| check_compliance | boolean | – | Check schema follows SDC4 principles. Default true. |
| instance_path | string | yes | Path to the XML instance file to validate. |
| schema_path | string | yes | Path to the SDC4 data model XSD file. |
No output schema declared.
No examples provided.
validate_instance ~92
Validate an XML instance against its SDC4 XSD schema. Returns pass/fail with error count and classified errors.
| Name | Type | Req | Description |
|---|---|---|---|
| check_compliance | boolean | – | Check schema follows SDC4 principles (no xsd:extension). Default true. |
| instance_path | string | yes | Path to the XML instance file to validate. |
| schema_path | string | yes | Path to the SDC4 data model XSD file. |
No output schema declared.
No examples provided.
How do I install the io.github.SemanticDataCharter/sdcvalidator MCP server?
io.github.SemanticDataCharter/sdcvalidator runs locally as a PyPI package, launched with uvx sdcvalidator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sdcvalidator
claude mcp add semanticdatacharter-sdcvalidator -- uvx sdcvalidator
What is the io.github.SemanticDataCharter/sdcvalidator MCP server?
io.github.SemanticDataCharter/sdcvalidator is an MCP server listed in the public MCP registry as io.github.SemanticDataCharter/sdcvalidator. SDC4 structural validator with ExceptionalValue recovery; thin wrapper over xmlschema. This page covers its PyPI package (sdcvalidator).
Is the io.github.SemanticDataCharter/sdcvalidator MCP server safe to use?
io.github.SemanticDataCharter/sdcvalidator scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.SemanticDataCharter/sdcvalidator MCP server expose?
io.github.SemanticDataCharter/sdcvalidator exposes 3 tools: validate_instance, validate_and_report, check_schema_compliance. Their descriptions and schemas cost roughly 228 tokens of context every time the server is loaded.
Is the io.github.SemanticDataCharter/sdcvalidator MCP server still maintained?
io.github.SemanticDataCharter/sdcvalidator 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 io.github.SemanticDataCharter/sdcvalidator MCP server under?
io.github.SemanticDataCharter/sdcvalidator declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.