Repository navigation
Add governance/security category and agent-governance server #978
Description
Proposal: Governance Category for MCP Server Registry
Summary
Add a "security" or "governance" category to the MCP Registry, and register a governance MCP server that provides policy enforcement, threat detection, and audit trails for any MCP client.
Why a Governance Category?
As the MCP ecosystem grows, organizations need a way to discover governance and security servers. The registry currently organizes servers by function but doesn't have a clear category for:
- Policy enforcement servers — Validate tool calls against organizational policies
- Security scanning servers — Detect threat patterns in tool arguments
- Audit/compliance servers — Generate and query audit trails
- Trust scoring servers — Score multi-agent delegation requests
Proposed Server Entry
{
"name": "agent-governance",
"description": "Policy enforcement, threat detection, trust scoring, and audit trails for MCP tool calls",
"repository": "https://github.com/imran-siddique/agentmesh-integrations",
"category": "security",
"tools": [
"governance_check_policy",
"governance_detect_threats",
"governance_score_trust",
"governance_audit_log",
"governance_audit_query"
],
"resources": [
"governance://policies/active",
"governance://audit/recent"
]
}Context
We maintain Agent-OS and AgentMesh governance frameworks. Related:
- modelcontextprotocol/servers #3352 — Governance MCP server proposal
- modelcontextprotocol/python-sdk #2094 — Governance middleware
- google/mcp-security #237 — MCP security governance extension
Activity
imran-siddique commentedon Mar 8, 2026
Closing - project moved to microsoft/agent-governance-toolkit. Will re-submit fresh proposals from the Microsoft repo. Thank you!
trimtab-signal commentedon Oct 20, 2026
P31 Sovereign Stack — Meta-Governance Entry
Server name:
com.p31ca/governnpm package: @p31ca/govern (v0.1.2, Sigstore provenance attestation)
Repository: p31labs/production
Description: The P31 universal governance runtime — validates constitutions, proves gates can fail, composes enterprise specs, reconciles timelines. Meta-governance: governance of the governance system itself.
Tools:
govern_validate— Validate a P31 domain constitution against schemagovern_self_test— Prove every gate can fail (negative controls)govern_compose— Compose enterprise constitution from domain specsgovern_reconcile— Reconcile enterprise timeline across domainsWhy governance category:
Microsoft's agent-governance-toolkit governs individual tool calls (pre-execution, runtime, post-execution). P31 governs the governance system itself — domain constitutions, gate proofs, runbook compliance, and release provenance. These are complementary: Microsoft governs agent actions; P31 governs the rules that govern agent actions.
Compile-or-reject standard: Every rule must produce a deterministic artifact (a gate), and every gate must be proven able to fail (a negative control). No furniture gates.
Provenance: @p31ca/govern@0.1.2 published via stage-only OIDC trusted publisher with Sigstore attestation. Bootstrap gap formally declared in BOOTSTRAP.md and closed with 0.1.2.
Registry listing:
server.jsonwithremotesarray (Streamable HTTP) ready for submission once endpoint is deployed.Positioning: The only governance framework whose release process is a governed domain with a stage-only OIDC trusted publisher, a human 2FA approval gate, and a signed provenance attestation.