sdcgovernance
OfficialRelated Servers
Alternatives to sdcgovernance
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server wrapping the toolgovern CLI as a single generic run tool for agent-tool policy validation.Apache 2.0

sdcvalidatorofficial
AlicenseAqualityBmaintenanceMCP server for validating SDC4 XML instances against XSD schemas, with two-tier error classification and SDC4 compliance checks.31Apache 2.0- AlicenseNot gradedqualityDmaintenanceMCP server for querying the DodaOne governance framework, enabling users to retrieve governance information and evaluate proposed actions.2 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a governance layer for MCP servers, enforcing policy-based allow/deny/approval rules, requiring human approval for risky calls, and recording an auditable trail of every AI agent tool call.MIT
- AlicenseBqualityDmaintenanceA governance and policy enforcement gateway for MCP servers that provides hard guardrails, dynamic parameter bounds, human-in-the-loop approvals, and audit telemetry.27 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server that evaluates agent actions against a Policy State Machine, emits a tamper-evident audit trail, and dispatches approved transitions to internal or federated handlers.-
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action, but there are two close pairs: get_allowed_transitions vs evaluate_transition (enumerate vs decide) and get_governance_status vs validate_governance (report dimensions vs validate an instance). Descriptions do make the boundaries explicit, so misselection risk is low but non-zero.
All nine tools follow a strict verb_noun snake_case pattern (evaluate_*, get_*, validate_*, record_*, register_*, list_*, verify_*). The repeated verbs are used semantically consistently, with no camelCase or bare-noun outliers.
Nine tools is squarely in the well-scoped range and each maps to a concrete governance step: policy registration, policy lookup, decision evaluation, governance validation, transition discovery/authorization, provenance, and evidence verification. No filler or duplicate tools.
Core lifecycle is covered: register/list/evaluate decision tables, validate governance, inspect and evaluate transitions, verify evidence packs. Gaps remain around provenance (record only, no read/query tool), no evidence pack construction (verify only), and no deprecation/removal for registered tables, but these are workaroundable rather than blocking.