Security Hub MCP Server
Offensive security tools like Nmap, Nuclei, and Radare2 for AI-driven vulnerability assessment.
Data last scanned today · Reviewed yesterday
Overview
Security Hub MCP Server provides a collection of 38 containerized servers offering access to over 300 security tools. These tools cover domains including reconnaissance, web security, binary analysis, and OSINT, enabling AI models to interact with security utilities through natural language. The project uses Docker Compose for orchestration and provides pre-configured templates for integration with Claude Desktop. Users can automate multi-tool workflows, with specific container configurations provided for tasks like network scanning, vulnerability discovery, and secrets detection.
Our verdict
This server is rated high risk with a security score of 27/100. The primary security concerns are the complete lack of an authentication method, meaning anyone with access to the configuration can execute these offensive tools, and the absence of read-only restrictions on many components. Due to the high risk and offensive nature of the tools provided, this should only be used in isolated, non-production environments by experienced security professionals.
- Supports 38 distinct MCP servers
- Integrates over 300 security tools
- Zero direct dependencies
- Active development with 740 GitHub stars
- No authentication method implemented
- Lacks native read-only mode across all tools
- Community-maintained rather than official vendor software
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the core prerequisites for running these servers?
You must have Docker installed, as these MCP servers are distributed as Docker containers and require Docker Compose for orchestration.
›Is it necessary to perform any initial setup before connecting the servers to Claude?
Yes, you must build the Docker images locally using the 'docker-compose build' command before they can be configured or used by your MCP client.
›How do I provide access to local files for analysis?
You must use Docker volume mounts within your configuration to grant the containers read-only access to specific directories containing your targets, such as source code or binaries.
›Are there any specific container privileges required for certain tools?
Yes, specific tools like Nmap require extra capabilities, such as '--cap-add=NET_RAW', to function correctly within the Docker container.
›Can these servers be used for automated CI/CD pipelines?
Yes, the repository is CI/CD ready and includes GitHub Actions configurations for automated builds and security scanning.
Alternatives
Badge
Maintain this server? Add the live badge to your README.