Skip to main content
Glama
Guardian by Odingard

Guardian by Odingard

Related Servers

Alternatives to Guardian by Odingard

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Wraps your existing MCP servers and checks each tool call against policy and live state before it runs. Allow, block, or require a refresh, with a reason the agent can act on.
      5
      -
    • A
      license
      B
      quality
      C
      maintenance
      Security gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed decision receipts. Shadow mode logs every tool call without blocking; enforce mode applies block, rate-limit, and minimum-tier rules. Receipts are independently verifiable offline with no accounts needed.
      5
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables wrapping existing MCP servers to intercept JSON-RPC tool calls and enforce declarative security policies with allow, deny, human-approval, secret-redaction, rate-limit, and tamper-evident audit-log capabilities.
      240 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enforces allow/deny/ask policies on MCP tool calls before they reach downstream servers, with tamper-evident audit logging.
      MIT
    • 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

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool has a distinct role: guardian_invoke_tool is the entry point for governed calls, guardian_claim executes an already-approved ASK request, and guardian_record is a read-only audit lookup. The claim/invoke boundary is slightly subtle because both can run a tool, but the descriptions clearly distinguish initiation from approval execution.

    Naming Consistency5/5

    All tools use the guardian_ prefix and snake_case, with predictable verb-oriented names (claim, invoke_tool, record). The convention is consistent throughout and easy to scan.

    Tool Count5/5

    Three tools are well matched to a narrowly scoped governance/approval wrapper: one to invoke, one to claim an approval, and one to inspect records. No tool feels redundant or missing for this purpose.

    Completeness4/5

    The surface covers the key decision lifecycle: invoke, defer to approval, claim after approval, and inspect evidence afterward. A minor gap is the lack of an explicit pending-request listing, though the external Guardian UI plausibly handles that workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues