Skip to main content
Glama

Related Servers

Alternatives to TurboPentest

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      MCP server for offensive-security tooling, enabling AI agents to run reconnaissance, CVE intelligence, JavaScript analysis, HTTP probing, and port scanning against authorized targets.
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      AI-powered penetration testing framework that can operate as an MCP server, enabling automated security assessments through natural language commands.
      2
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that integrates various penetration testing tools, enabling security professionals to perform reconnaissance, vulnerability scanning, and API testing through natural language commands in compatible LLM clients like Claude Desktop.
      7
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      A penetration testing MCP server that runs 20 hacking tools inside a Kali Linux Docker container, enabling AI assistants to execute security scans and attacks via natural language.
      2
      -

    TDQS

    A4.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    The four workflow_* tools return instructions rather than performing actions, and are clearly distinguished from the actual action tools (start_pentest, get_findings) by their descriptions. Minor overlap risk exists — an agent could confuse workflow_run_pentest with start_pentest, or workflow_analyze_findings with get_findings — but the descriptions explicitly clarify each tool's role.

    Naming Consistency4/5

    All names use snake_case with a consistent turbopentest_ prefix followed by verb_noun (get_credits, list_domains, start_pentest, get_pentest, get_findings, download_report). The workflow_* group inserts a noun segment before the verb, which is a minor deviation but is internally consistent across all four tools.

    Tool Count5/5

    Twelve tools is well within a comfortable range and each tool maps to a distinct operation in the pentest lifecycle. No redundant or filler tools are present.

    Completeness4/5

    The surface covers credits, domain listing, launching, listing, monitoring, findings retrieval, reporting, and attestation verification — a strong full-lifecycle flow. Minor gaps exist: domain addition/verification must be done via the dashboard, and there is no tool to cancel or delete a running pentest, but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues