VulneraMCP
# VulneraMCP
> **An AI-Powered Bug Bounty MCP Server** ā recon, vulnerability testing, API/auth/cloud scanning, graph analysis, and reporting for security researchers and bug bounty hunters.
[](https://opensource.org/licenses/MIT)
[](https://www.typescriptlang.org/)
[](https://nodejs.org/)
[](https://youtu.be/wlUvBVNyh74)
[](https://glama.ai/mcp/servers/telmon95/VulneraMCP)
<a href="https://glama.ai/mcp/servers/telmon95/VulneraMCP"><img src="https://glama.ai/mcp/servers/telmon95/VulneraMCP/badges/score.svg"></a>
VulneraMCP is a Model Context Protocol (MCP) server for bug bounty hunting and security testing. It integrates OWASP ZAP, optional Caido/Burp Suite, and CLI tools (subfinder, httpx, gau, ffuf) for reconnaissance, JavaScript analysis, XSS/SQLi/IDOR/CSRF testing, API and auth misconfiguration checks, cloud bucket and secret scanning, orchestrated scan flows, knowledge-graph analysis, wordlist generation, and Markdown reporting ā with PostgreSQL storage for findings and test results.
## š¬ Demo
Watch the VulneraMCP demonstration on YouTube: [https://youtu.be/wlUvBVNyh74](https://youtu.be/wlUvBVNyh74?si=643DdGkLSH40jUMe)
## š Features
### š Reconnaissance Tools
- **Subdomain Discovery**: Subfinder, Amass integration
- **Live Host Detection**: HTTPx for checking active endpoints
- **DNS Resolution**: DNS record enumeration (A, AAAA, CNAME, MX, TXT)
- **URL Discovery**: Gau (Get All URLs) from archives and crawlers
- **Fuzzing**: ffuf for directory, file, and parameter discovery
- **Full Recon Workflow**: Automated multi-tool reconnaissance
### š Security Testing
- **XSS Testing**: Automated cross-site scripting detection
- **SQL Injection**: SQLi vulnerability testing with sqlmap fallback
- **IDOR Detection**: Insecure Direct Object Reference testing
- **CSP Analysis**: Content Security Policy misconfiguration detection
- **Auth Bypass**: Authentication bypass attempt testing
- **CSRF Testing**: Cross-Site Request Forgery detection with advanced techniques
### š API Testing
- **GraphQL**: Introspection and misconfiguration checks
- **Rate Limiting**: Endpoint rate limit testing
- **BOLA / IDOR**: Broken object level authorization tests
- **Mass Assignment**: Unsafe field assignment detection
- **Swagger/OpenAPI**: API documentation enumeration
### š Authentication Testing
- **JWT**: None algorithm and algorithm confusion attacks
- **OAuth**: Misconfiguration detection
- **Session**: Fixation and cookie flag analysis
- **Password Reset**: Host header poisoning tests
- **MFA**: Bypass signal detection and testing
### āļø Cloud Security
- **Storage**: S3/Azure/GCP bucket enumeration and permission probes
- **Secrets**: Exposed key scanning in JS, HTML, and env files
- **Terraform**: State file leak detection
### šÆ Scanner Orchestration
- **Target Normalization**: Standardize targets for multi-tool flows
- **Run Flow**: Orchestrated scanning across API, auth, and cloud tools
- **Finding Correlation**: Link and correlate results across tests
### š Graph Analysis
- **Knowledge Graph**: Store targets, findings, and relationships in PostgreSQL
- **Pattern Detection**: Extract patterns and find similar findings
- **Attack Graphs**: Generate, rank, and export attack paths (JSON, GraphML)
### š Reporting & Wordlists
- **Report Generation**: Markdown reports from findings
- **Wordlist Generation**: Directories, files, parameters, and combined lists
### š JavaScript Analysis
- **JS Download**: Download and analyze JavaScript files
- **Code Beautification**: Format and beautify minified JS
- **Endpoint Extraction**: Find API endpoints and URLs in JS
- **Secret Detection**: Heuristic API key and token extraction
- **Full Analysis**: Combined download, beautify, and analyze workflow
### š·ļø Integration
- **Spider Scans**: Automated web crawling
- **Active Scanning**: Vulnerability scanning
- **Proxy Integration**: Process requests through ZAP proxy
- **Alert Management**: Retrieve and analyze security alerts
- **Context Management**: Define scanning contexts
### š¾ Database Integration
- **PostgreSQL**: Store findings, test results, and scores
- **Redis**: Working memory and caching (optional)
- **Finding Management**: Save and retrieve bug findings
- **Test Result Storage**: Track all security tests with statistics
### š¼ļø Rendering Tools
- **Screenshots**: Capture webpage screenshots with Puppeteer
- **DOM Extraction**: Extract and analyze page structure
- **Form Extraction**: Find and analyze web forms
- **JavaScript Execution**: Execute JS in page context
### š¤ AI Training & Pattern Matching
- **Training Data Import**: Import from HTB, PortSwigger labs
- **Pattern Matching**: Learn from successful exploits
- **Writeup Analysis**: Extract patterns from bug bounty writeups
- **CSRF Patterns**: Pre-loaded CSRF exploitation patterns
### š Web Dashboard
- **Real-time Statistics**: View test results and findings
- **Finding Management**: Browse and analyze discovered vulnerabilities
- **Visual Analytics**: Track testing progress and success rates
## š Quick Start
### Prerequisites
- **Node.js** 20+ and npm
- **PostgreSQL** 18+ (or Docker)
- **Redis** (optional, for caching)
- **ZAP** (optional, for active scanning)
- **Caido** (optional, for traffic analysis)
### Installation
```bash
# Clone the repository
git clone https://github.com/telmon95/VulneraMCP.git
cd VulneraMCP
# Install dependencies
npm install
# Build the project
npm run build
```
### Configuration
1. **Copy environment template:**
```bash
cp mcp.json.example mcp.json
```
2. **Configure your environment variables:**
- Set up PostgreSQL connection details
- Configure Caido API token (if using)
- Set ZAP API URL (default: http://localhost:8081)
3. **Initialize the database:**
```bash
node init-db.js
```
### Running the Server
```bash
# Start the MCP server
npm start
# Start the dashboard (in another terminal)
npm run dashboard
# Access dashboard at http://localhost:3000
```
### Docker Setup
```bash
# Start all services with Docker Compose
docker-compose up -d
# Or use the startup script
./start-services.sh
```
## š Usage
### Via MCP Client (Cursor, Claude Desktop, etc.)
The server provides MCP tools that can be called through any MCP-compatible client:
**Reconnaissance:**
```
recon.subfinder domain: example.com
recon.httpx input: example.com,subdomain.example.com
recon.full domain: example.com
```
**Security Testing:**
```
security.test_xss url: https://example.com/search?q=<script>
security.test_sqli url: https://example.com/user?id=1
security.test_csrf url: https://example.com/profile/update
```
**JavaScript Analysis:**
```
js.analyze url: https://example.com/static/app.js
js.extract_secrets source: <javascript_code>
```
**ZAP Integration:**
```
zap.start_spider url: https://example.com
zap.start_active_scan url: https://example.com
zap.get_alerts baseURL: https://example.com
```
**Caido Integration:**
```
caido.query httpql: "req.host.cont:\"example.com\" AND req.path.cont:\"api\""
caido.agent_discover_endpoints host: example.com
```
### Rate Limiting & Best Practices
When testing bug bounty programs, always respect rate limits:
```javascript
// Example: 2 requests/second limit
const rateLimiter = require('./hunting/rate-limiter');
const limiter = rateLimiter(2); // 2 req/sec
await limiter();
// Make your request
```
## šļø Project Structure
```
VulneraMCP/
āāā src/
ā āāā integrations/ # External service integrations
ā ā āāā zap.ts # OWASP ZAP integration
ā ā āāā caido.ts # Caido integration
ā ā āāā postgres.ts # PostgreSQL database
ā ā āāā redis.ts # Redis caching
ā āāā tools/ # MCP tools (recon, security, etc.)
ā āāā mcp/ # MCP server implementation
ā āāā index.ts # Main entry point
āāā public/ # Dashboard frontend
āāā hunting/ # Bug bounty hunting scripts
āāā dist/ # Compiled TypeScript output
āāā dashboard-server.js # Dashboard API server
```
## š§ Configuration
### MCP Server Configuration (`mcp.json`)
```json
{
"name": "vulneramcp",
"command": "node",
"args": ["dist/index.js"],
"env": {
"POSTGRES_HOST": "localhost",
"POSTGRES_PORT": "5433",
"POSTGRES_USER": "postgres",
"POSTGRES_DB": "bugbounty"
}
}
```
### Environment Variables
```bash
# PostgreSQL
POSTGRES_HOST=localhost
POSTGRES_PORT=5433
POSTGRES_USER=postgres
POSTGRES_PASSWORD=your_password
POSTGRES_DB=bugbounty
# ZAP
ZAP_API_URL=http://localhost:8081
# Caido
CAIDO_API_TOKEN=your_token
# Redis (optional)
REDIS_HOST=localhost
REDIS_PORT=6379
```
## š Dashboard
The web dashboard provides:
- **Statistics**: Test results, success rates, vulnerability distribution
- **Findings**: Detailed view of discovered vulnerabilities
- **Search & Filter**: Find specific findings by target, type, severity
Access at: `http://localhost:3000`
## š Sponsor
If VulneraMCP helps your bug bounty or security research workflow, consider sponsoring development on [GitHub Sponsors](https://github.com/sponsors/telmon95).
Your support helps fund new features, documentation, security testing, and long-term maintenance of this open source project.
## š¤ Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
1. Fork the repository
2. Create your feature branch (`git checkout -b feature/AmazingFeature`)
3. Commit your changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request
## š License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
## ā ļø Disclaimer
This tool is for authorized security testing only. Always:
- Get proper authorization before testing
- Respect rate limits and terms of service
- Follow responsible disclosure practices
- Never use on systems you don't own or have explicit permission to test
## š Acknowledgments
- ZAP for vulnerability scanning
- The bug bounty community for inspiration and feedback
## š Documentation
- [Quick Start Guide](QUICK_START.md)
- [ZAP Integration](ZAP_INTEGRATION.md)
- [Dashboard Guide](DASHBOARD_README.md)
- [Training Data](TRAINING.md)
## š Issues
Found a bug? Have a feature request? Please open an issue on [GitHub](https://github.com/telmon95/VulneraMCP/issues).
## š§ Contact
- GitHub: [@telmon95](https://github.com/telmon95)
- Sponsors: [GitHub Sponsors](https://github.com/sponsors/telmon95)
- Issues: [GitHub Issues](https://github.com/telmon95/VulneraMCP/issues)
TDQS
Scored across 47 tools
The tools are well-organized into clear functional categories (db, js, recon, render, security, training, zap), which helps disambiguation significantly. However, within categories like 'training' there are multiple import tools (import, import_all, import_htb, import_portswigger) that could cause confusion about which to use for specific scenarios. The overall structure prevents major misselection issues.
Excellent naming consistency throughout. All tools follow a consistent 'category.action' pattern (e.g., 'db.get_findings', 'js.analyze', 'security.test_xss'). The verb_noun structure is maintained within each category, and there's no mixing of naming conventions. This predictability makes the tool set easy to navigate.
With 47 tools, this server feels overloaded for a single MCP server. While the domain (vulnerability assessment) is broad, the tool count creates cognitive overhead and suggests the server might be trying to do too much. A more focused approach with 15-25 tools would likely be more appropriate for agent usability.
The tool surface provides comprehensive coverage of the vulnerability assessment domain. It includes database operations, JavaScript analysis, reconnaissance, rendering, security testing, training data management, and ZAP integration. The tools support complete workflows from reconnaissance through testing to result analysis, with no obvious gaps in the core functionality.