Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
SDC4 structural validator with ExceptionalValue recovery; thin wrapper over xmlschema.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"sdcvalidator": {
"command": "uvx",
"args": [
"sdcvalidator",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add sdcvalidator -- uvx sdcvalidator mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sdcvalidator": {
"command": "uvx",
"args": [
"sdcvalidator",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"sdcvalidator": {
"type": "stdio",
"command": "uvx",
"args": [
"sdcvalidator",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account SemanticDataCharter, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (4.6.3) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
SDC4 structural validator — a thin wrapper over xmlschema with two-tier error classification.
xsd:extension — only xsd:restriction)pip install sdcvalidator
Or from source:
git clone https://github.com/SemanticDataCharter/sdcvalidator.git
cd sdcvalidator pip install -e .
from sdcvalidator import SDC4Validator, ErrorTier
validator = SDC4Validator("my_schema.xsd") result = validator.validate("my_instance.xml")
if result.is_valid: print("Valid!") else: for err in result.structural_errors: print(f"STRUCTURAL: {err.reason}") for err in result.semantic_errors: print(f"SEMANTIC: {err.reason}")
The validation parameter controls how strictly the XSD schema itself is checked when loaded:
XMLSchemaParseError if the schema contains invalid restriction derivations (e.g., element names that don't match the base type). This is the recommended mode.# Explicit lax mode for legacy schemas
validator = SDC4Validator("legacy_schema.xsd", validation='lax')
from sdcvalidator import validate_sdc4_schema_compliance, assert_sdc4_schema_compliance
is_valid, errors = validate_sdc4_schema_compliance("schema.xsd")
assert_sdc4_schema_compliance("schema.xsd")
from sdcvalidator import ErrorClassifier, ErrorTier
classifier = ErrorClassifier() tier = classifier.classify(some_xmlschema_error)
A semantic (Tier 2) error does not have to reject a record. Recovery keeps the value and inserts an ISO 21090 ExceptionalValue beside it (Invalid, for a value that fails its type, pattern, range or enumeration), so the record says which value is unusable and why, and the rest of it stays usable.
from sdcvalidator import SDC4Validator, SDC4UnrecoverableError
v = SDC4Validator("dm-xxxx.xsd", validation="lax") result = v.recover("record.xml") # RecoveryResult; the source is never mutated for r in result.recoveries: # Recovery: path, code ("INV"), name, reason, inserted print(r.code, r.reason, r.path) if not result.ok: # an error no ExceptionalValue covers print(result.unrecoverable)
tree = v.validate_with_recovery("record.xml", save=False) # raises SDC4UnrecoverableError instead
remove_existing_ev=True removes them first.unrecoverable by recover(), and raised as SDC4UnrecoverableError by validate_with_recovery(); it is never skipped.SDC4StructuralValidationError.XMLResource when the record carries prefixed QNames in content (xsi:type="sdc4:...").from sdcvalidator.converters import xml_to_json, json_to_xml
data = xml_to_json("instance.xml", schema_path="schema.xsd")
json_to_xml(data, "schema.xsd", "output.xml")
sdcvalidate — Validate XML against schema# Basic validation
sdcvalidate schema.xsd instance.xml
sdcvalidate schema.xsd instance.xml --json
sdcvalidate --no-compliance-check schema.xsd instance.xml
Exit codes: 0 valid, 1 semantic errors only, 2 structural errors.
sdcvalidator-xml2json — Convert XML to JSONsdcvalidator-xml2json instance.xml --schema schema.xsd
sdcvalidator-xml2json instance.xml -o output.json
sdcvalidator-json2xml — Convert JSON to XMLsdcvalidator-json2xml data.json schema.xsd -o output.xml
sdcvalidator ships a stdio MCP (Model Context Protocol) server so any MCP-capable agent can validate SDC4 data without importing the Python library. It implements JSON-RPC 2.0 directly over stdio — no external MCP SDK dependency.
sdcvalidator # what an MCP registry client runs (uvx sdcvalidator)
sdcvalidator mcp # the same, spelled like the other Semantic Data Charter servers sdcvalidator-mcp serve --mcp # still works for existing client configurations
A client configuration needs only "command": "uvx", "args": ["sdcvalidator"].
| Tool | Purpose |
|---|---|
validate_instance | Validate an XML instance against its SDC4 XSD schema. Returns pass/fail with error count and classified errors. |
validate_and_report | Validate an instance and return a detailed report with two-tier (structural vs semantic) error classification. |
check_schema_compliance | Check whether an XSD schema follows SDC4 principles (restriction only, no xsd:extension). Does not validate instances. |
validate_instance and validate_and_report take schema_path and instance_path, plus an optional check_compliance boolean (default true). check_schema_compliance takes schema_path only.
| Tier | Type | Examples | Action |
|---|---|---|---|
| 1 | Structural | Unknown elements, cardinality violations, wrong nesting | Reject |
| 2 | Semantic | Type errors, pattern violations, enumeration mismatches | Report, or recover with an ExceptionalValue |
SDC4 data models must use xsd:restriction only — never xsd:extension. This enforces separation of structure (reference model) and semantics (data models), guaranteeing global interoperability.
The validator checks this by default and rejects schemas that violate this principle.
Production-ready. Available on PyPI under Apache 2.0.
Apache License 2.0 — see LICENSE.