Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SapperMCP

No user-submitted related servers found.

    Related Servers

    • Pentest MCP

      Holland8079
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables professional penetration testers to run reconnaissance, exploitation, password cracking, web fuzzing, vulnerability scanning, traffic capture, and client-reporting workflows through MCP transports with auth support.
      165 npm
      GPL 3.0

    • security-framework-mcp

      zer0-kr
      A
      license
      A
      quality
      D
      maintenance
      Unified MCP server integrating NIST and OWASP security frameworks with live vulnerability data, enabling security searches, compliance mapping, threat modeling, and checklist generation.
      41
      14
      MIT

    • OpenCyber Harness

      mitkox
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides an MCP stdio interface to 253 security tools across software and physical layers, with isolated engagement workspaces, serial sessions, firmware triage, scoped HTTP/browser automation, and hash-chained audit evidence for authorized red- and blue-team work.
      1
      Apache 2.0

    • Xolotl

      Ricardoarangob26
      A
      license
      B
      quality
      B
      maintenance
      Unifies seven open-source security scanners into one MCP interface, normalizing and deduplicating findings with AI-assisted triage, patch verification, and reports. Enables agents to scan source code, dependencies, secrets, containers, infrastructure-as-code, and authorized live targets under server-enforced safety limits.
      18
      1
      MIT

    • Pentest MCP

      aPhillips0102
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables professional penetration testers to run reconnaissance, network and web scanning, content fuzzing, vulnerability templates, brute-force checks, SQLi extraction, traffic capture, and engagement report generation through MCP clients.
      165 npm
      GPL 3.0

    • Pentest MCP

      erkut9520
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables authorized penetration testers to run reconnaissance, scanning, brute-force, traffic-capture, and exploitation tools through MCP clients, with authentication, engagement recordkeeping, and client report generation.
      165 npm
      GPL 3.0
    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

    C2.7/5.0

    Scored across 127 tools

    Disambiguation2/5

    While most tools map to a distinct resource/action, several clusters have genuinely unclear boundaries: the autonomous drivers (sapper_auto, sapper_command, sapper_sweep, sapper_bench, sapper_dispatch) all 'advance a graph toward the goal,' and sapper_pick vs sapper_claim vs sapper_frontier vs sapper_brainstorm_pick overlap on selection. Duplicated pairs like press_key/send_key_combo and list_windows/find_windows_by_title/find_windows_by_process, plus the all-encompassing sapper_cli and run_command vs run_argv, force an agent to reason about escaping/indirection before choosing.

    Naming Consistency3/5

    Everything is snake_case and the sapper_/package_/gsettings_ prefixes group families sensibly, but conventions within families are mixed: some tools are verb_noun (get_process_info, list_windows, capture_screen), others are noun-only or bare verbs (click, double_click, sapper_status, sapper_board, sapper_report, package_info), and vague verbs like manage_service and sapper_handle-style catch-alls break the predictiveness.

    Tool Count2/5

    127 tools is far past the point where an agent can reliably select the right one, even though the surface spans several legitimately distinct domains (system/process admin, packages, desktop automation, file IO, the sapper graph, PTY sessions). The breadth partly justifies the size, but the count should be split into separate servers or collapsed behind fewer parameterized tools.

    Completeness4/5

    Coverage is unusually thorough: file CRUD plus metadata/permissions, full process and service lifecycle, package management, desktop input/capture/clipboard, PTY sessions, and a complete fact/intent graph lifecycle with validation, reporting, and visualization. Minor gaps remain (no graph fact/intent edit or delete, no kb entry update/delete, no append-file primitive, no image clipboard), but agents can work around them.

    Resources