Skip to main content
Glama
Sanflow10

adversary-gate

by Sanflow10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to adversary-gate

No user-submitted related servers found.

    Related Servers

    • phionyx-pipeline-mcp

      halvrenofviryel
      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
      AGPL 3.0

    • Task Handoff Verifier

      Harmantaj
      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

    • agent-guardrail

      ss1738
      A
      license
      Not graded
      quality
      A
      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
    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.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    verify_repo executes tests and judges the working tree, while gate_policy returns read-only enforcement information. These purposes are completely distinct with no overlap, so an agent can easily select the right tool.

    Naming Consistency3/5

    Both names use snake_case, but verify_repo follows a clear verb_noun pattern while gate_policy is a bare noun phrase. This mixes action-oriented and resource-oriented conventions, though both remain readable.

    Tool Count3/5

    With only two tools, the surface feels thin even for a focused verification server. The tools are well-chosen but leave no room for auxiliary operations like baseline introspection.

    Completeness4/5

    The core verification and policy-reading operations are present, covering the main lifecycle for an adversary gate. Minor gaps exist, such as retrieving baseline details or historical gate results, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources