io.github.SemanticDataCharter/sdcgovernance
PYPI · SDCGOVERNANCE
Governance validation for Semantic Data Charter instances; returns OASIS XACML decisions.
Available components
Last scanned (8 hours ago)
Scores higher than 90% of PyPI servers
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
- 1 of 11 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SemanticDataCharter/sdcgovernance). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1476 tokens (~164/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 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.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +1
- Package version: 4.2.4 → 4.3.1 functional
- 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.
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/sdcgovernance@4.3.1
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/sdcgovernance |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SemanticDataCharter/sdcgovernance/.github/workflows/release.yml@refs/tags/v4.3.1 |
| Rekor log index | 3465920753 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:642ecf2da08444d618fc1524c446a33eacf27d11408b07feb2d0fec4b6075649 |
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 11 packages
| Packages resolved | 11 |
|---|---|
| Stale | 1 |
| 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 →
evaluate_decision ~543
Evaluate a DMN decision table against instance context. Name the table by table_id (and table_version; the highest registered version when omitted) for a governed evaluation, or pass it inline as table_json for an ad-hoc one. Returns decision, matched_rules, reasoning, errors, the table's identity and content hash, and a tamper-evident Receipt whose receipt_hash covers table_id, table_version and table_hash as well as context_hash. instance_path is optional: when omitted, the decision is evaluated against extra_context alone, which is the path external context-only consumers (e.g. MTCP Evidence Packs) should use. Pass previous_hash to chain receipts; the caller is responsible for chain persistence.
| Name | Type | Req | Description |
|---|---|---|---|
| context_hash | string | – | SHA-256 hash of the extra_context payload, computed by the caller. Binds the Receipt cryptographically to the context that produced the decision. MTCP consumers pass the Evidence Pack hash here. |
| extra_context | string | – | JSON string with additional context key-value pairs. |
| instance_id | string | – | Identifier for the entity being evaluated, recorded in the Receipt. For SDC instances this is the DM instance_id (CUID2). For external consumers this is the entity identifier (e.g. an MTCP model_id s… |
| instance_path | string | – | Path to the XML instance file for context extraction. Optional. Omit to evaluate against extra_context only. |
| instance_version | string | – | Version of the entity being evaluated, recorded in the Receipt. |
| previous_hash | string|null | – | SHA-256 hash of the prior Receipt in the caller's chain. Pass null (default) to start a new chain. The caller is responsible for chain persistence. |
| table_id | string | – | Id of a registered decision table (see register_decision_table and list_decision_tables). Give table_id or table_json, not both. |
| table_json | string | – | JSON string defining the decision table inline, for an ad-hoc evaluation (the Receipt then carries the table's content hash but no id or version). Format: {"name": "...", "hit_policy": "FIRST|UNIQUE|… |
| table_version | string | – | Version of the registered table. Omit for the highest registered version; the Receipt records the version that was used. |
No output schema declared.
No examples provided.
evaluate_transition ~90
Evaluate whether a specific workflow transition is permitted. Returns PERMIT/DENY/INDETERMINATE with receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | Identity of the actor requesting the transition. |
| instance_path | string | yes | Path to the XML instance file. |
| schema_path | string | yes | Path to the SDC data model XSD file. |
| target_state | string | yes | Proposed target state symbol. |
No output schema declared.
No examples provided.
get_allowed_transitions ~70
Get valid next states from the current workflow state. Returns list of valid transitions with target state info and path(s).
| Name | Type | Req | Description |
|---|---|---|---|
| instance_path | string | yes | Path to the XML instance file containing workflow and current-state. |
| schema_path | string | yes | Path to the SDC data model XSD file. |
No output schema declared.
No examples provided.
get_governance_status ~53
Report which governance dimensions the model defines. Returns model_id, model_label, has_governance, and active dimensions.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_path | string | yes | Path to the SDC data model XSD file. |
No output schema declared.
No examples provided.
list_decision_tables ~108
List the registered decision tables: table_id, version, table_hash, domain, policy and registered_at for each version, lowest version first. Filter by table_id or domain. With table_id the full table JSON of each version is included, which is how a receipt's table_id and table_version are resolved back to the rules that applied.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Only tables registered under this domain. |
| table_id | string | – | Only this table's versions, with their JSON. |
No output schema declared.
No examples provided.
record_provenance ~154
Record a provenance event as a W3C PROV-O record. Returns the PROV record content.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_type | string | yes | W3C Activity Streams 2.0 type (Create, Update, Accept, etc.) |
| agent_name | string | yes | Name of the agent performing the action. |
| agent_ref | string | – | URI reference for the agent. |
| description | string | – | Human-readable description. |
| entity_hash_after | string | – | SHA-256 hash after action. |
| entity_hash_before | string | – | SHA-256 hash before action. |
| entity_id | string | – | ID of the entity (DM.instance_id). |
| system_id | string | – | System that produced this record. |
No output schema declared.
No examples provided.
register_decision_table ~238
Register a decision table under a stable table_id and an immutable version, so evaluate_decision can name it and every Receipt it produces records which policy version applied. Returns table_id, version, table_hash (SHA-256 of the table's RFC 8785 canonical JSON), domain and policy. Registering the same content again under the same id and version is a no-op; different content under an existing id and version is refused: register it as a new version. Persists to the server's tables directory when one is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional domain the table governs, e.g. 'retention' or 'escalation'. |
| policy | string | – | Optional policy reference the table implements, e.g. a policy document URI. |
| table_id | string | yes | Stable identifier, e.g. 'cordova.access-control'. Letters, digits, '.', '_', '-'. |
| table_json | string | yes | JSON string defining the decision table (same format as evaluate_decision). |
| version | string | yes | Immutable version label, e.g. '1.0' or '2026-10-18'. |
No output schema declared.
No examples provided.
validate_governance ~77
Full governance validation of an instance against its model. Returns decision, has_governance, errors, dimensions_validated.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_path | string | – | Path to the XML instance file. Optional - if omitted, returns model governance status only. |
| schema_path | string | yes | Path to the SDC data model XSD file. |
No output schema declared.
No examples provided.
verify_evidence_pack ~97
Verify the integrity of an MTCP Evidence Pack by recomputing its evidence_pack_hash. Returns valid (bool), computed_hash, and expected_hash. Canonicalization follows RFC 8785: keys sorted, no whitespace, comma-colon separators, UTF-8.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_pack | string | yes | JSON string of the MTCP Evidence Pack including its evidence_pack_hash field. Hash is recomputed over the remaining fields and compared. |
No output schema declared.
No examples provided.
How do I install the io.github.SemanticDataCharter/sdcgovernance MCP server?
io.github.SemanticDataCharter/sdcgovernance runs locally as a PyPI package, launched with uvx sdcgovernance. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sdcgovernance
claude mcp add semanticdatacharter-sdcgovernance -- uvx sdcgovernance
What is the io.github.SemanticDataCharter/sdcgovernance MCP server?
io.github.SemanticDataCharter/sdcgovernance is an MCP server listed in the public MCP registry as io.github.SemanticDataCharter/sdcgovernance. Governance validation for Semantic Data Charter instances; returns OASIS XACML decisions. This page covers its PyPI package (sdcgovernance).
Is the io.github.SemanticDataCharter/sdcgovernance MCP server safe to use?
io.github.SemanticDataCharter/sdcgovernance scores 88 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/sdcgovernance MCP server expose?
io.github.SemanticDataCharter/sdcgovernance exposes 9 tools: get_governance_status, get_allowed_transitions, evaluate_transition, validate_governance, record_provenance, and 4 more. Their descriptions and schemas cost roughly 1,430 tokens of context every time the server is loaded.
Is the io.github.SemanticDataCharter/sdcgovernance MCP server still maintained?
io.github.SemanticDataCharter/sdcgovernance 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/sdcgovernance MCP server under?
io.github.SemanticDataCharter/sdcgovernance 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.