/ Directory / Playground / mcp-security-hub
● Community FuzzingLabs ⚡ Instant

mcp-security-hub

by FuzzingLabs · FuzzingLabs/mcp-security-hub

38 Dockerized MCP servers packaging 300+ security tools — Nmap, Nuclei, SQLMap, Ghidra, Hashcat, and more for AI assistants.

mcp-security-hub is a collection of 38 production-ready, Dockerized MCP servers integrating 300+ offensive security tools with AI assistants. Covers reconnaissance (Nmap, Shodan, Masscan), web security (Nuclei, SQLMap, FFUF), binary analysis (Radare2, Ghidra, YARA), cloud security (Trivy, Prowler), blockchain (Medusa), OSINT (Gitleaks, Bloodhound), and more. Docker Compose orchestration with security-hardened containers.

Why use it

Key features

Live Demo

What it looks like in practice

mcp-security-hub.replay ▶ ready
0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "mcp-security-hub": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/FuzzingLabs/mcp-security-hub"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "mcp-security-hub": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/FuzzingLabs/mcp-security-hub"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "mcp-security-hub": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/FuzzingLabs/mcp-security-hub"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "mcp-security-hub": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/FuzzingLabs/mcp-security-hub"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "mcp-security-hub",
      "command": "TODO",
      "args": [
        "See README: https://github.com/FuzzingLabs/mcp-security-hub"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "mcp-security-hub": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/FuzzingLabs/mcp-security-hub"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add mcp-security-hub -- TODO 'See README: https://github.com/FuzzingLabs/mcp-security-hub'

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use mcp-security-hub

How to run automated reconnaissance with mcp-security-hub

👤 Security professionals conducting authorized assessments ⏱ ~60 min intermediate

When to use: You need to run multiple recon tools against an authorized target.

Prerequisites
  • Docker and Docker Compose installed — Install Docker Desktop or Docker Engine
  • Written authorization for the target — Signed penetration testing agreement
Flow
  1. Start recon tools
    Start the nmap-mcp and nuclei-mcp servers. Run port scanning and vulnerability scanning against the authorized target at 192.168.1.100.✓ Copied
    → Port scan results and vulnerability findings
  2. Deep dive on findings
    Found a web server on port 443. Run FFUF for directory fuzzing and check for common web vulnerabilities with Nuclei.✓ Copied
    → Directory listing and vulnerability scan results

Outcome: Comprehensive reconnaissance results from multiple tools.

Pitfalls
  • Running all 38 servers at once consumes significant resources — Only start the servers you need. Use docker-compose up with specific service names.
Combine with: filesystem

Analyze a CTF binary with containerized reverse engineering tools

👤 CTF participants working on binary challenges ⏱ ~30 min intermediate

When to use: You have a binary to reverse engineer and want containerized analysis tools.

Prerequisites
  • Docker with security-hub cloned — git clone && docker-compose build
Flow
  1. Analyze the binary
    Start the radare2-mcp server. Load the CTF binary and show me the function list, strings, and entry point disassembly.✓ Copied
    → Binary overview with interesting functions and strings

Outcome: Binary analysis insights from containerized tools.

Pitfalls
  • Binary needs host-specific libraries — Mount the binary directory into the container, or use the YARA/Capa servers for static analysis

Combinations

Pair with other MCPs for X10 leverage

mcp-security-hub + filesystem

Save all security assessment results to organized report files

Run a full recon suite on the target and compile results into a pentest report at ~/reports/assessment.md.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
nmap-mcp target, options Network port scanning 0
nuclei-mcp target, templates? Template-based vulnerability scanning 0
sqlmap-mcp url, params? SQL injection testing 0
radare2-mcp binary_path, command Binary reverse engineering 0
trivy-mcp target_image Container and IaC vulnerability scanning 0

Cost & Limits

What this costs to run

API quota
N/A — all tools run locally in Docker
Tokens per call
300–3000 tokens per tool output
Monetary
Free — all tools are open source. Shodan/similar may need their own API keys.
Tip
Only start servers you need. docker-compose up nmap-mcp nuclei-mcp instead of all 38.

Security

Permissions, secrets, blast radius

Credential storage: Individual tool API keys (Shodan, etc.) via Docker env vars
Data egress: Scans connect to target IPs. OSINT tools call their respective APIs.

Troubleshooting

Common errors and fixes

Docker build fails

Ensure Docker is installed and running. Some tools may need updated base images.

Verify: docker --version && docker compose --version
Container can't reach target

Check Docker network settings. Use host networking mode for network scanning tools.

Verify: docker exec <container> ping <target>
Out of disk space

Docker images can be large. Prune unused images: docker system prune

Verify: docker system df

Alternatives

mcp-security-hub vs others

AlternativeWhen to use it insteadTradeoff
hexstrike-aiYou want AI agents that autonomously orchestrate security toolsMore AI intelligence but less Docker isolation
mcp-kali-serverYou want a lightweight bridge to a full Kali installation instead of DockerSimpler setup but less isolation

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills