Skip to main content
Glama
sipkigroup

deus-witness

by sipkigroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to deus-witness

No user-submitted related servers found.

    Related Servers

    • agent-firewall

      beernathan87
      A
      license
      Not graded
      quality
      C
      maintenance
      Sits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.
      MIT

    • AgentGuard

      Davin-06
      A
      license
      Not graded
      quality
      C
      maintenance
      A transparent MCP stdio proxy that sits between an agent client and a real MCP server, intercepting tools/call requests to enforce runtime guardrails derived from the same YAML rules used for CI regression testing. It blocks forbidden, out-of-whitelist, looping, or non-idempotent tool invocations with JSON-RPC errors and writes every decision to an audit log.
      1
      MIT
    • Proofpane by Proofpane

      Proofpaneofficial

      Proofpane
      A
      license
      B
      quality
      A
      maintenance
      A governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.
      13
      MIT

    • cordon

      marras0914
      A
      license
      Not graded
      quality
      C
      maintenance
      Security gateway for MCP tool calls. Sits between your LLM client and MCP servers, enforcing per-tool policies (allow/block/approve/read-only), logging every call, and pausing dangerous operations for human approval in terminal or Slack.
      4 npm
      2
      MIT

    • okgate

      ubukhari
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP policy proxy that sits between AI agents and their upstream MCP servers to enforce hard spend and blast-radius caps, human approvals for destructive tools, a kill switch, scoped per-agent credentials, dry-run writes with mutation diffs, semantic loop breaking, and a hash-chained audit log. It also offers hook mode that applies the same policy to coding agents' own shell commands and file edits.
      MIT

    • AgentGuard MCP Server

      vaasu202
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.
      -
    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

    B3.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action and resource type: email, purchase, deletion, publishing, and file reading. There is little risk of an agent confusing one tool with another.

    Naming Consistency3/5

    Most names use verb_noun form (send_email, delete_resource, read_file), but purchase and publish are standalone verbs. The conventions are mixed but still readable and predictable enough.

    Tool Count5/5

    Five tools is a reasonable, compact set. Each tool represents a distinct operation, so the count is well-scoped rather than bloated.

    Completeness2/5

    The surface is disjointed: delete_resource exists with no create/update/read resource tools, read_file has no write counterpart, and purchase/send_email/publish have no lifecycle operations. This leaves significant gaps for most plausible domains.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources