Practical overview
When it fits
Use it when you want to connect an MCP-compatible assistant to a selection of security tools and can build and configure the relevant Dockerized servers.
Who it is for
- Security practitioners who want to access supported tools through an MCP-compatible AI assistant.
- Developers configuring MCP integrations or assembling Docker-based security workflows.
Documented uses
- Connect an assistant to selected tools such as Nmap, Nuclei, SQLMap or Ghidra.
- Build and start selected MCP server containers with Docker Compose.
- Configure Claude Desktop, Claude Code or a project-level MCP configuration to reference server images.
- Make security assessment and binary-analysis tools available through assistant-facing workflows.
Requirements & limits
The repository is public and identifies an MIT license. Its documented setup uses Docker Compose and includes configuration examples for Claude Desktop and Claude Code.
- The collection spans multiple security areas, so choose the server integrations relevant to the task rather than treating the Hub as one scanner.
- The README lists 38 MCP servers and more than 300 tools; these are repository claims, not a count independently tested here.
- Images must be built before the documented Claude configuration can use them.
- Some configuration examples use volume mounts to expose local repositories or binaries to a container.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build and start selected MCP servers
Build the repository’s Docker Compose services and start the Nmap and Nuclei servers.
Before you start
- The MCP Security Hub repository
- Docker and Docker Compose
Steps
Clone the repository and change into its directory.
Run
docker-compose buildto build the MCP server images.Run
docker-compose up nmap-mcp nuclei-mcp -dto start those services.Run
docker-compose psto inspect service status.
Expected outcome
The selected Nmap and Nuclei services are started through Docker Compose, and their listed status can be inspected.
Guide limitations
- This sequence does not configure an MCP client to connect to the services.
- The README states that images must be built before they are used.
Prepare a Claude MCP configuration
Add example MCP server entries to a Claude Desktop configuration after building the corresponding images.
Before you start
- Docker
- A Claude Desktop or Claude Code configuration
- Built images for the servers being configured
Steps
Build the required server images with
docker-compose build.Copy the example configuration to the Claude Desktop configuration location for macOS or Windows.
Use the README’s JSON example to add entries for the selected servers, such as Nmap or Nuclei.
For project-level configuration, copy
.mcp.jsonto the project root.
Expected outcome
A Claude configuration file contains example MCP server entries for the selected Docker images.
Guide limitations
- The README requires building images first.
- The configuration example is a setup instruction; it does not establish that a particular local environment has successfully connected.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- FuzzingLabs/mcp-security-hub · Official homepage title · retained in its source language

