Skip to main content
Glama
Sign In
agentguard-run

agentguard

Official
by agentguard-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agentguard

No user-submitted related servers found.

    Related Servers

    • mneme-ai

      patsa2561-art
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate through a local, signed boundary that blocks prompt injection and secret leakage, verifies outputs, preserves cross-session memory, and provides offline-verifiable receipts. It also exposes 900+ MCP tools for discoverable agent actions.
      7
      MIT
    • Affixio MCP by AffixIO

      Affixio MCPofficial

      AffixIO
      A
      license
      A
      quality
      A
      maintenance
      Enables agents to locally attest actions and gate privileged tool calls with signed allow/deny decisions, using privacy-preserving hashing and offline ML-DSA-65 verification.
      3
      7 npm
      Apache 2.0

    • Vizier

      vassiliylakhonin
      A
      license
      A
      quality
      A
      maintenance
      Owner-signed authorization before agent actions. Hosted Vizier v0.5.13 MCP: https://vizier.agendamcp.dpdns.org/mcp. ALLOW/BLOCK/REVIEW; anonymous calls never ALLOW. Your integration enforces the decision. SDK v0.5.13: https://www.npmjs.com/package/@agenda-intelligence/vizier-sdk. Grants are signed; legacy receipts are unsigned. Python stdio is a separate catalog.
      3
      7 npm
      MIT

    • veor

      winterbim
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.
      MIT

    • eidolon-gateway

      gegane-lutshaba
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to govern downstream tool servers by enforcing default-deny authority and attestation on every tool call, with live monitoring, approval, and mid-session revocation.
      3
      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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct function: preview, status, export, set cost, decide, and verify. The repeated optional identifier language adds some textual similarity, but the core purposes are clearly separate, with only mild potential overlap between preview and status.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (provenance_preview, spend_status, export_receipts, set_model_cost, spend_decide, verify_receipt). The verbs are descriptive and the nouns align with the API's domain, making the naming pattern highly predictable.

    Tool Count5/5

    With 6 tools, the server is well-scoped. Each tool serves a distinct role in the spend-gating and receipt lifecycle, and none feel redundant or missing a critical counterpart. This is an appropriate count for a focused security/attestation service.

    Completeness4/5

    The tool set covers the core workflow: previewing provenance, checking status, setting model costs, making decisions, exporting receipts, and verifying them. Missing is a tool to modify policy (caps, enforcement mode), which is only exposed read-only via spend_status. This is a minor gap that an agent could work around if policies are managed externally.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources