Skip to main content
Glama

Related Servers

Alternatives to adversary-gate

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables verification of AI coding agent self-reports against git diff truth and a deterministic gate, producing pass/regenerate/reject directives to ensure claimed work matches actual changes.
      6
      22 PyPI
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents a local, mechanical workflow authority: an agent's issue claim is recorded, every subsequent write and irreversible step (push, merge, tag, release) is re-verified against that record, and review verdicts are bound to exact commit bytes so a later push invalidates them. Refusals report what was read and what to do next, keeping an unreadable tracker distinct from a forbidden action.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude to independently check an AI agent's work in a local git repository by recording a baseline, running only the checks relevant to the changed files, and cross-checking what the agent claimed. Returns a compact, evidence-labelled report with a verdict and a ready-to-paste next prompt, so unverified success claims can't slip through.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.
      1
      MIT

    TDQS

    A4.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    verify_repo runs the gate and returns a decision, while gate_policy is a fast read-only dump of the enforced policy; the descriptions explicitly frame one as the action and the other as the pre-flight/explanation lookup. There is no plausible way to misselect between them.

    Naming Consistency5/5

    Both names use a consistent snake_case verb_noun pattern (verify_repo, gate_policy) and share the server's 'gate' vocabulary. No mixing of camelCase, prefixes, or verb styles.

    Tool Count3/5

    Two tools is thin, but the server has a deliberately narrow remit: enforce one verification gate. Still, the policy/verification split is the only structure present, so the count is borderline rather than well-scoped.

    Completeness4/5

    The pair covers the whole stated workflow: learn the policy, then run the gate, with arguments for claims, pytest args, base_ref, and timeout. Minor gaps remain (no read-only way to inspect baseline commit/tree or preview discovered claims without executing the suite), but agents can work around them.

    Maintenance

    ActivityNo data
    ResponsivenessResponsive