Skip to main content
Glama
mimaworks

mimaworks/governance-mcp

Official
by mimaworks

Related Servers

Alternatives to mimaworks/governance-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      MCP server that auto-emits tamper-evident receipts for every tool call, enabling EU AI Act Article 12 compliance with signed, chain-linked receipts.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
      30
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for compliance automation of AI agents, enabling EU AI Act compliance, verifiable credentials, and decentralized identity management with 47 tools across 9 modules.
      45 PyPI
      17
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI compliance auditing. Scores agent outputs for hallucination liability under the EU AI Act, issues verifiable compliance stamps, and tracks audit history by agent.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing immutable audit logging, policy enforcement, and compliance reporting for AI agent workflows, enabling regulatory compliance and chain integrity verification.
      MIT

    TDQS

    A4.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct governance action: attest vs dry_run_attest are clearly write vs preview, get_posture vs check_gates differentiate overall scores from deployment blockers, and list_systems vs list_evidence separate system registry from evidence ledger. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent lowercase verb_noun or verb pattern: get_posture, check_gates, list_systems, register_system, acknowledge_policy, suggest_gates. The compound 'dry_run_attest' is a clear modifier of the base verb 'attest', maintaining consistency.

    Tool Count5/5

    With 10 tools, the server is well-scoped for AI governance: registration, evidence recording, posture checks, gate management, and gap analysis. Each tool earns its place without redundancy or bloat.

    Completeness5/5

    The surface covers the full governance lifecycle: register systems, attest evidence (with dry-run preview), check posture and gates, derive controls for gaps, and list evidence/systems for audits. Evidence is immutable by design, so no update/delete is needed. The only minor gap might be direct gate configuration, but suggest_gates covers recommendations adequately.

    Maintenance

    ActivityStale
    ResponsivenessNo issues