Get the FREE Ultimate OpenClaw Setup Guide โ†’

pentesting-cyber

๐Ÿ” 50+ MCP Security Servers for AI-Powered Pentesting | Integrate Nmap, Burp Suite, Nuclei, Shodan, BloodHound, Semgrep, Trivy | Model Context Protocol for Cybersecurity

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio hackersatyamrastogi-pentesting-cyber-mcp node path/to/servers/nmap/build/index.js /usr/bin/nmap

How to use

This MCP server collection exposes a standardized interface to fifty security tooling options through the MCP protocol. Each tool is wrapped behind its own MCP server entry, allowing clients to connect, request capabilities, and execute commands in a uniform way. The provided examples show how to run individual tools locally, such as Nmap for network discovery, Nuclei for vulnerability scanning, Metasploit for exploitation workflows, and a unified server to access all tools through a single connection. Clients can leverage the MCP protocol to discover available capabilities, submit tasks, and aggregate results in a consistent format across tools.

How to install

Prerequisites:

  • Node.js 18+
  • The underlying security tools (e.g., nmap, nuclei, msfconsole, sqlmap) installed on your system
  • Git and a package manager (pnpm recommended by the project)

Install and build steps:

  1. Clone the repository: git clone https://github.com/hackersatyamrastogi/pentesting-cyber-mcp.git cd pentesting-cyber-mcp

  2. Install dependencies: pnpm install

  3. Build all servers (or build individually): pnpm build

    Or build a specific server

    cd servers/nmap && pnpm build

  4. Run an individual MCP server to verify: node servers/nmap/build/index.js /usr/bin/nmap node servers/nuclei/build/index.js /usr/bin/nuclei node servers/metasploit/build/index.js msfconsole

  5. Configure MCP client to connect to these servers as shown in the Configuration section of the README.

Additional notes

Tips and notes:

  • Ensure the underlying tools are installed and reachable at the paths used in the args (e.g., /usr/bin/nmap).
  • The unified server entry provides access to all tools through a single MCP connection, which can simplify client integration.
  • If you encounter permission issues running tools like nmap or msfconsole, validate that the user running the MCP server has the necessary privileges.
  • Review tool-specific documentation within the repo for any tool-specific environment requirements or arguments.
  • The repository supports multiple MCP servers; use the mcp client configuration example to wire up the exact set of servers you plan to use.

Related MCP Servers

Sponsor this space

Reach thousands of developers โ†—