zebbern-kali-mcp
Integrates 121 penetration testing tools into AI workflows, enabling security teams to automate vulnerability discovery and compliance validation without con…
MCP server for Kali Linux penetration testing - 121 tools for AI-assisted security testing - Giving Agents access to full pentesting tools
- Ask Claude to run network vulnerability scans and identify exposed ports on target systems.
- Generate penetration test reports by automating security tool execution and result analysis.
- Find weak cryptographic implementations by running hash cracking and encryption analysis tools.
Integrates 121 penetration testing tools into AI workflows, enabling security teams to automate vulnerability discovery and compliance validation without context-switching between tools and agents.
Security engineering teams and penetration testers automating reconnaissance, scanning, and exploitation workflows within AI-assisted security assessments.
https://github.com/zebbern/zebbern-kali-mcp
By zebbern
How to Get It
claude mcp add zebbern-kali-mcp -- npx -y zebbern-kali-mcp
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Run network vulnerability scans and identify exposed ports on target systems
Trust Signals Auto-scanned
Data & Access
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 45 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 45 GitHub stars; contributors unknown; last commit 0d ago; license MIT.