Skip to main content
Glama
bsahane

kali-mcp-server

by bsahane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to kali-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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.
      172 npm
      GPL 3.0

    • kali-mcps

      Diaz673
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to run Kali Linux security tools through MCP clients for network scanning, binary and symbol analysis, string extraction, live packet capture, traffic inspection, and sandboxed command execution in Docker containers.
      -

    • kali-mcps

      konstantinyoshida
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables security testing and reverse engineering through MCP clients by providing Kali Linux tools for network scanning, binary and symbol analysis, string extraction, packet capture/analysis, and sandboxed Docker command execution.
      -

    • kali-mcps

      Serkan53740
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to run Kali Linux security and reverse-engineering tools for network scanning, binary and symbol analysis, string extraction, live/PCAP traffic analysis, and isolated Docker-based command execution.
      -
    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

    A4/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., nmap_scan vs masscan_scan vs host_discovery). However, dns_recon with scan_type 'brt' overlaps with subdomain_enum, and several *scan tools could be confused by target type, though descriptions clarify.

    Naming Consistency4/5

    All tool names use snake_case and mostly follow a '{object}_{action}' pattern (dns_recon, nmap_scan, hash_crack). Exceptions like list_tools_status, generate_report, and record_finding start with a verb, creating minor inconsistency but still predictable.

    Tool Count4/5

    24 tools is above the typical 3-15 range, but the server covers a full pentest workflow (recon, scanning, exploitation, reporting, scope management). Each tool serves a distinct function, so the count feels slightly heavy but justified for a Kali MCP server.

    Completeness4/5

    The toolset covers the core lifecycle: recon (dns_recon, subdomain_enum), scanning (nmap_scan, nikto_scan), exploitation (sqlmap_test, hydra_bruteforce), and reporting (record_finding, generate_report). Minor gaps like traffic capture or wireless testing exist, but the main engagement flow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources