Skip to main content
Glama
yagobski

AgentLeak

by yagobski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to AgentLeak

No user-submitted related servers found.

    Related Servers

    • TrustHarness

      ofirtro
      A
      license
      B
      quality
      C
      maintenance
      Enables deterministic security testing of AI agents that use tools by serving synthetic MCP environments with poisoned data, fake secrets, and privileged actions. Records agent tool calls and evaluates security invariants (e.g., canary leaks, forbidden access, approval binding) without an LLM judge or real systems.
      8
      MIT

    • TracePII Shield MCP

      clauxel
      F
      license
      Not graded
      quality
      F
      maintenance
      Redacts PII from LLM traces and tool payloads before they leave review, enabling PII scanning, payload redaction, sensitive field classification, privacy receipts, and trace audit exports.
      -

    • ARGUS

      CerisonAutomation
      F
      license
      B
      quality
      C
      maintenance
      Enables AI agents to perform comprehensive, zero-infrastructure codebase analysis through 24 MCP tools, covering security, quality, architecture, type safety, git history, and dead code detection with high precision and local privacy.
      45
      -
    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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools target distinct concerns: delta-aware project check, static code scan, single-run trace scoring, and text redaction. However, privacy_preflight and privacy_scan_code overlap substantially (preflight is essentially scan plus a delta and optional trace scoring), so an agent must rely on the descriptions to choose correctly rather than on clearly separate purposes.

    Naming Consistency4/5

    All names share the privacy_ prefix and are snake_case, giving a strong, predictable family. Minor deviation: scan_code and check_trace follow a verb_noun shape while preflight and redact are verb/noun-only, so the action pattern isn't perfectly uniform.

    Tool Count5/5

    Four tools is a tight, well-scoped surface for a privacy-auditing server, and each one covers a distinct mode of use (pre-ship delta check, static scan, trace scoring, redaction). No tool looks redundant or bolted on.

    Completeness4/5

    The lifecycle is largely covered: detect (scan), detect-and-diff (preflight), deep channel analysis (trace), and remediate (redact). Gaps exist around retrieving or listing prior findings, configuring policy/severity thresholds, and verifiable proof of remediation, but these are workaroundable.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources