Skip to main content
Glama
io.github.datumline/agent-guard

io.github.datumline/agent-guard

Official
by datumline

Related Servers

Alternatives to io.github.datumline/agent-guard

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to submit AI agent claims for verification, read verdicts, and fetch or offline-verify signed receipts.
      7
      35 npm
      2
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables agents and clients to fact-check factual claims against live web sources, returning citable verdicts with source details and cryptographically signed receipts for downstream verification.
      1
      102 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and orchestrators to deterministically verify sub-agent outputs inside the loop, catching placeholders, unbacked claims, stale state, count mismatches, and missing components before acting on claimed completion. It also supports failure reports and hash-chained verification receipts.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic verification of AI agent decisions and actions, providing PASS/FAIL/ABSTAIN verdicts with replayable proofs and an optional signed receipt ledger.
      4 npm
      Apache 2.0

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of selecting the wrong tool or confusing it with another operation. Its purpose is clearly scoped to verifying an agent's completion claim against artifacts.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun convention: verify_completion_claim. With only one tool there are no conflicting naming styles or inconsistent patterns.

    Tool Count3/5

    The server has a very narrow purpose, so one focused tool is defensible, but a single-tool surface is thin for an MCP server. It lacks companion operations such as listing or retrieving prior verification receipts.

    Completeness4/5

    The tool covers several artifact types and clear verdicts, which addresses the core verification workflow well. Minor gaps remain around receipt retrieval, history, or manifest management, but agents can work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues