Skip to main content
Glama
scopeguard-mcp

scopeguard-mcp

by Wsh7Ash

Related Servers

Alternatives to scopeguard-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to conduct authorized pentests and bug-bounty workflows with scope enforcement, audit logging, reconnaissance, safe vulnerability checks, payload/wordlist generation, and professional report generation.
      14
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform safe, authorized penetration testing by managing engagements, enforcing scope and risk policies, and orchestrating tools like Nmap, Nuclei, and Subfinder.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform authorized web-pentest reconnaissance and interaction, including crawling, headless-browser control, login/BOLA comparisons, safe probes, HAR replay, and evidence-first reporting, while enforcing declared scope, audit trails, rate limits, and data minimization.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables authorized AI pentest agents to use typed HTTP, DNS, TCP, TLS, and finding tools through a scope-enforcing gateway that quarantines hostile target content and records hash-chained evidence.
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables authorized autonomous application and API security testing, allowing LLM-driven agents to plan and execute pentest checks while a deterministic policy layer enforces scope and authorization outside the model.
      -

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct primary action: scope checking, CVSS scoring, redaction, reading findings, and appending findings. There is mild conceptual overlap because add_finding internally re-checks scope and redacts evidence, but the descriptions make clear that check_target and redact are standalone utilities while add_finding is the enforced write path.

    Naming Consistency3/5

    Three tools follow a clear verb_noun snake_case pattern (check_target, list_findings, add_finding), but cvss_base is a noun phrase and redact is a bare verb. The set remains readable and all lowercase snake_case, but the convention is not uniform.

    Tool Count5/5

    Five tools is well-scoped for a narrow scope-guard and findings-ledger server. Each tool maps to a necessary step in the workflow: validate scope, score severity, sanitize text, and read/write findings.

    Completeness3/5

    The surface covers scope checking, scoring, redaction, and append/read of findings, but the ledger lacks get-by-id, update, delete, or filtering operations, and there is no tool for managing or listing the authorized scope rules themselves. Some gaps may be intentional for an append-only ledger, but agents will hit dead ends when correcting or querying findings.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data