Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Governance validation for Semantic Data Charter instances; returns OASIS XACML decisions.
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": {
"sdcgovernance": {
"command": "uvx",
"args": [
"sdcgovernance",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add sdcgovernance -- uvx sdcgovernance mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sdcgovernance": {
"command": "uvx",
"args": [
"sdcgovernance",
"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": {
"sdcgovernance": {
"type": "stdio",
"command": "uvx",
"args": [
"sdcgovernance",
"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 7, 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.3.1) reached the registry 13 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, Foliosio
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.
Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.
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.
W3C standards-based governance advisory engine for Semantic Data Charter instances.
A Python library that validates governance content in XML data instances against governance components defined in the SDC data model. If the model defines governance (workflow, attestation, party/role, provenance, audit), the instance must carry that content - and this library validates it.
Returns decisions using OASIS XACML semantics: PERMIT, DENY, or INDETERMINATE.
No framework dependency. No middleware. A function call.
SDC data models (XSD) can optionally include governance components: Workflow state machines, Attestation authority requirements, Party/Role constraints, Provenance requirements, and Audit definitions. These are part of the data model, not a separate governance layer.
When governance components are defined, every XML data instance must carry the corresponding governance content. This library validates that content against the model:
from sdcgovernance import validate_governance
result = validate_governance("model.xsd", "instance.xml")
print(result.decision) # PERMIT, DENY, or INDETERMINATE print(result.has_governance) # True if model defines governance components print(result.errors) # list of governance validation errors print(result.receipt) # tamper-evident decision receipt
If the model does not define governance components, the result is PERMIT - no governance to enforce.
sdcvalidator and sdcgovernance are separate, independent libraries. There is no hook, no chaining, no automatic invocation of one from the other.
sdcvalidator (structural validation)
Does the instance conform to the XSD schema? Single-pass. Instance in, pass/fail out.
sdcgovernance (governance advisory) Does the model define governance components? If yes: does the instance carry valid governance content? Conversational. Agents query multiple times during a workflow.
Both libraries read the schema from the instance. Agents call each one independently, at different points in a workflow, in whatever order the operational logic requires. A single workflow may involve multiple calls to both libraries.
| Component | What the model defines | What the instance must carry |
|---|---|---|
| Workflow | Cluster tree of valid paths (sub-clusters with XdOrdinal states) | Current XdOrdinal state, proposed transition validated against ordinal adjacency in valid paths |
| Attestation | Authority requirements per action | Attestation with correct role, party reference, timestamp |
| Party/Role | Role constraints for governed actions | Acting party identification with required role |
| Provenance/Audit | Provenance requirements (PROV-O) + retention policy (DPV) | PROV-formatted record(s) per retention policy: most recent + hash, last N, or full chain |
Governance components are discovered by their position in the DMType root (fixed RM slots: workflow, attestation, party/role, audit, and related), not by CUID2 identity. Once a slot is found, its content is validated by vocabulary binding against the relevant standard (PROV-O, SCXML, VC, DPV). Any component occupying the right slot and bound to the right vocabulary is recognized - whether it comes from the Default project or was custom-built.
| Decision | Meaning |
|---|---|
| PERMIT | All governance checks pass - action is authorized |
| DENY | One or more governance checks fail - action is refused |
| INDETERMINATE | Governance checks partially pass - requires review (configurable) |
Every decision produces a W3C PROV record and a SHA-256 hash-chained receipt.
What happens after the decision is the agent's responsibility. sdcgovernance issues the decision and the receipt. The operational response - routing, escalation, notification, halting - is customer business logic that varies per implementation.
Python API - for direct integration:
from sdcgovernance import validate_governance
result = validate_governance("model.xsd", "instance.xml")
MCP Server - for any agent framework:
sdcgovernance # what an MCP registry client runs (uvx sdcgovernance)
sdcgovernance mcp # the same, spelled like the other Semantic Data Charter servers sdcgovernance serve --mcp # still works for existing client configurations
A client configuration needs only "command": "uvx", "args": ["sdcgovernance"].
The MCP server exposes governance as tools that agents call. The agent runs the loop. sdcgovernance advises.
src/sdcgovernance/
├── init.py # Public API: validate_governance() ├── engine.py # GovernanceEngine - the decision engine agents query ├── model_inspector.py # Inspect SDC model for governance components ├── workflow.py # Validate workflow transitions in instance ├── attestation.py # Validate attestation content in instance ├── party_role.py # Validate party/role constraints in instance ├── provenance.py # Validate provenance/audit records + PROV generation + DPV retention policy ├── decision.py # DMN decision table evaluation + content hash ├── tables.py # Decision table registry: id, version, hash; files on disk ├── receipts.py # Decision receipt chain (hash-chained) ├── shacl_runtime.py # SHACL cross-entity constraint validation └── mcp_server.py # MCP server exposing governance tools to any agent
Pure Python. No Django. No middleware. No web framework dependency.
pip install sdcgovernance
validate_governance() at data entry boundaries.Production-ready. Available on PyPI under Apache 2.0.
rdflib - RDF/PROV record generationpyshacl - SHACL constraint validationApache 2.0