Skip to main content
Glama
holdout-labs

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
      38 npm
      1
      Apache 2.0

    • LedgerProof LAIN

      vsdawkins-creator
      F
      license
      Not graded
      quality
      C
      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 by vaibot-io

      @vaibot/mcp-serverofficial

      vaibot-io
      F
      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
      -

    • 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
      C
      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.
      1
      -
    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 distinct lifecycle role: initialize, attach evidence, execute governance checks, and read-only inspection. There is no overlap or ambiguity between the four tools.

    Naming Consistency5/5

    All tool names follow a clear gov_<verb> pattern with consistent snake_case naming. The prefix clearly groups them under the same domain while the verb indicates the action.

    Tool Count5/5

    Four tools is a tight, well-scoped set that covers the governance workflow without redundancy. Each tool earns its place and the count feels appropriate for the server's purpose.

    Completeness5/5

    The tool set covers the full lifecycle: scaffold the project, attach evidence and reviews, view state without side effects, and run the authoritative gate check. No critical operation appears missing for the stated governance workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources