mcp-security-hub MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

38 Dockerized MCP servers covering all major security domains
300+ integrated security tools accessible via natural language
Security-hardened containers: non-root, dropped capabilities, read-only mounts
CI/CD integration with automated builds and Trivy vulnerability scanning
Docker Compose for multi-tool workflow orchestration

Demo en vivo

Cómo se ve en la práctica

mcp-security-hub.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/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"
      ]
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.cursor/mcp.json · .cursor/mcp.json

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

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

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

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: mcp-security-hub

How to run automated reconnaissance with mcp-security-hub

👤 Security professionals conducting authorized assessments ⏱ ~60 min intermediate

Cuándo usarlo: You need to run multiple recon tools against an authorized target.

Requisitos previos

Docker and Docker Compose installed — Install Docker Desktop or Docker Engine
Written authorization for the target — Signed penetration testing agreement

Flujo

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.✓ Copiado

→ Port scan results and vulnerability findings
Deep dive on findings

Found a web server on port 443. Run FFUF for directory fuzzing and check for common web vulnerabilities with Nuclei.✓ Copiado

→ Directory listing and vulnerability scan results

Resultado: Comprehensive reconnaissance results from multiple tools.

Errores comunes

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

Combinar con: filesystem

Analyze a CTF binary with containerized reverse engineering tools

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

Cuándo usarlo: You have a binary to reverse engineer and want containerized analysis tools.

Requisitos previos

Docker with security-hub cloned — git clone && docker-compose build

Flujo

Analyze the binary

Start the radare2-mcp server. Load the CTF binary and show me the function list, strings, and entry point disassembly.✓ Copiado

→ Binary overview with interesting functions and strings

Resultado: Binary analysis insights from containerized tools.

Errores comunes

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

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

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.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar
nmap-mcp	target, options	Network port scanning
nuclei-mcp	target, templates?	Template-based vulnerability scanning
sqlmap-mcp	url, params?	SQL injection testing
radare2-mcp	binary_path, command	Binary reverse engineering
trivy-mcp	target_image	Container and IaC vulnerability scanning

Coste y límites

Lo que cuesta ejecutarlo

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

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: Individual tool API keys (Shodan, etc.) via Docker env vars

Salida de datos: Scans connect to target IPs. OSINT tools call their respective APIs.

⚠ This tool is designed for authorized security research, CTF competitions, and defensive analysis only. Do not use it against systems you don't own or have written authorization to test.
Containers are security-hardened but still execute real offensive tools.
Unauthorized scanning or exploitation is illegal. Always have written authorization.

Resolución de problemas

Errores comunes y soluciones

Docker build fails

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

Verificar: docker --version && docker compose --version

Container can't reach target

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

Verificar: docker exec <container> ping <target>

Out of disk space

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

Verificar: docker system df

Alternativas

mcp-security-hub vs otros

Alternativa	Cuándo usarla	Contrapartida
hexstrike-ai	You want AI agents that autonomously orchestrate security tools	More AI intelligence but less Docker isolation
mcp-kali-server	You want a lightweight bridge to a full Kali installation instead of Docker	Simpler setup but less isolation

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills