Skip to main content
Glama
Sign In
holdout-governance

holdout-governance

Official
by holdout-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to holdout-governance

No user-submitted related servers found.

    Related Servers

    • audit-ledger-mcp

      shahidh68
      A
      license
      A
      quality
      D
      maintenance
      Tamper-evident audit logging for AI decisions. Three tools (record_decision, verify_decision, list_decisions) write to a regulator-grade ledger built on AWS S3 Object Lock with 7-year retention. Designed for EU AI Act Article 12 and FCA SS1/23 evidence requirements. Try zero-config: npx audit-ledger-mcp boots in sandbox mode against a public hosted tenant.
      3
      92 npm
      1
      Apache 2.0

    • LedgerProof LAIN

      vsdawkins-creator
      F
      license
      Not graded
      quality
      D
      maintenance
      Cryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.
      -
    • @vaibot/mcp-server

      @vaibot/mcp-serverofficial

      vaibot-io
      A
      license
      A
      quality
      D
      maintenance
      Governance circuit-breaker MCP server that enables AI agents to request risk-based decisions, approve or deny actions, and finalize outcomes with full audit receipts.
      4
      MIT

    • sigmodx-mcp

      Sigmodx
      A
      license
      A
      quality
      D
      maintenance
      Audit infrastructure for AI agents to log consequential decisions (invoice, GL, anomaly) and verify attestations via MCP tools.
      6
      MIT

    • governed-mcp

      rsiraj0
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enforces governance on agentic decisions with auditable evidence records, providing tools for understanding, calibrating confidence, and navigating handoffs based on policy.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: gov_init scaffolds, gov_attach records evidence, gov_check executes gates and returns a verdict, and gov_report reads state without mutating. Descriptions explicitly contrast gov_report (read-only) against gov_check (fresh execution), removing the main risk of confusion. No overlapping or redundant tools.

    Naming Consistency5/5

    All four tools follow the same gov_ prefix with a consistent short verb (init, attach, check, report). The pattern is perfectly predictable across the set.

    Tool Count5/5

    Four tools map cleanly onto a linear workflow (scaffold → attach → decide → inspect), each earning its place with no filler. The count is well-scoped for the domain.

    Completeness4/5

    The toolset covers the full lifecycle init → attach → check → report, with no dead ends in the primary flow. Minor gaps exist (e.g. no explicit tool to list/inspect multiple artifacts or revoke a prior decision), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources