Skip to main content
Glama
sidclawhq

SidClaw GovernanceMCPServer

by sidclawhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to SidClaw GovernanceMCPServer

No user-submitted related servers found.

    Related Servers

    • mcpclerk

      hishamalward
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a governance proxy layer for MCP servers, enforcing per-tool allowlists, human approval for write operations, quotas, secret redaction, and a hash-chained audit log of all calls.
      MIT

    • mcp-gatekeeper

      saimsheikh
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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

    • safe-mcp-bridge-v2

      efe-arv
      A
      license
      Not graded
      quality
      C
      maintenance
      A fail-closed policy boundary that translates local stdio MCP clients to authenticated Streamable HTTP servers, enforcing allowlists or read-only modes and redacting credentials from audit trails.
      Apache 2.0

    • Agentrim MCP

      almohtadyg1
      A
      license
      Not graded
      quality
      B
      maintenance
      A least-privilege enforcement proxy for MCP servers. It sits between MCP clients and upstream servers, enforcing tool policies, hiding denied tools, requiring human approval for risky actions, and providing a structured audit trail.
      MIT
    • Agentomy MCP Gateway by getagentomy

      Agentomy MCP Gatewayofficial

      getagentomy
      A
      license
      Not graded
      quality
      C
      maintenance
      Governs any stdio MCP server by interposing between the agent and the server, enforcing policy on every tools/call and refusing denied actions before they reach the upstream server.
      13 npm
      Apache 2.0
    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

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool available, there is zero risk of an agent confusing it with another tool or selecting the wrong one. The tool's purpose as a proxy wrapper is distinct by default.

    Naming Consistency5/5

    The single tool uses clear snake_case formatting (governance_proxy). With only one tool in the set, it is trivially consistent with itself and follows a readable noun_noun pattern.

    Tool Count3/5

    One tool is borderline thin for a 'Governance' server, which typically implies multiple concerns (policy management, audit review, configuration). While the proxy mechanism is functional, the surface feels minimal for the stated scope.

    Completeness2/5

    Major gaps exist for the governance domain: there are no tools to configure policies, retrieve audit trails, check approval queue status, or manage the governance lifecycle. The server only provides the proxy wrapper without exposing its own governance data or settings to agents.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources