MCP-Connect — Kali Agent MCP v2
Related Servers
Alternatives to MCP-Connect — Kali Agent MCP v2
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProduction-grade MCP server that exposes Kali Linux penetration testing tools to AI agents, enabling automated reconnaissance, web application testing, vulnerability assessment, and more.-
- AlicenseNot gradedqualityBmaintenanceConfig-driven MCP server that exposes Kali Linux penetration testing tools to AI agents, with automatic tool discovery, man page integration, and local/remote execution modes.MIT
- FlicenseNot gradedqualityCmaintenanceA 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-
- FlicenseCqualityBmaintenanceMCP server that gives AI agents direct access to a Kali Linux penetration testing toolkit, with 155 tools for network scanning, exploitation, forensics, and more.100-
- AlicenseNot gradedqualityCmaintenanceLocal MCP server enabling Codex and ChatGPT to read/write files, execute commands, manage processes, use Git, and inspect images on the user's machine with full privileges.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Kali Linux MCP server that integrates network security and penetration testing tools like Nmap, Whois, Dig, Ping, Nikto, Hydra, and SQLMap into a Dockerized environment for use with LLMs.12 npm3-
TDQS
Scored across 126 tools
Many tools are well-differentiated by domain prefixes (browser_, docker_, git_, etc.), but exec_command and execute_command are nearly identical, causing confusion. Also, some tools like find_entrypoints and find_tests could overlap with search_text, though descriptions help.
Most tools follow a consistent verb_noun snake_case pattern (e.g., create_directory, list_directory). Minor inconsistencies exist, such as browser_console (noun) instead of get_console, but overall the naming is reasonably predictable.
126 tools is excessive for any server. While it aims to cover a broad security toolkit, many tools could be consolidated (e.g., a single run_security_tool with options). The sheer number overwhelms the agent's ability to select appropriately.
The tool set is extremely comprehensive, covering files, git, Docker, browser automation, process management, services, and a wide range of security scanners. However, there are minor gaps (e.g., no tool for chaining commands or updating scan configurations).