CyberMCP
# š CyberMCP
**AI-powered Cybersecurity API Testing with Model Context Protocol (MCP)**
[](https://opensource.org/licenses/MIT)
[](https://nodejs.org/)
[](https://www.typescriptlang.org/)
CyberMCP is a Model Context Protocol (MCP) server that enables AI agents to perform comprehensive security testing on backend APIs. It provides 14 specialized security tools and 10 resources for identifying vulnerabilities like authentication bypass, injection attacks, data leakage, and security misconfigurations.
## š Quick Start
```bash
# Clone and setup
git clone https://github.com/your-username/CyberMCP.git
cd CyberMCP
npm install
npm run build
# Test the server
npm run test-server
# Start interactive testing
npm run test-interactive
```
## āØ Features
- **š Authentication Testing** - JWT analysis, bypass detection, OAuth2 flows
- **š Injection Testing** - SQL injection, XSS vulnerability detection
- **š Data Protection** - Sensitive data exposure, path traversal checks
- **ā±ļø Rate Limiting** - DoS vulnerability assessment
- **š”ļø Security Headers** - OWASP security header validation
- **š Comprehensive Resources** - Security checklists and testing guides
## š ļø Security Tools (14 Total)
| Category | Tools |
|----------|-------|
| **Authentication** | `basic_auth`, `token_auth`, `oauth2_auth`, `api_login`, `auth_status`, `clear_auth`, `jwt_vulnerability_check`, `auth_bypass_check` |
| **Injection Testing** | `sql_injection_check`, `xss_check` |
| **Data Protection** | `sensitive_data_check`, `path_traversal_check` |
| **Infrastructure** | `rate_limit_check`, `security_headers_check` |
## šÆ IDE Integration
CyberMCP works with all major AI-powered IDEs:
- **Claude Desktop** - Direct MCP integration
- **Cursor IDE** - Built-in MCP support
- **Windsurf (Codeium)** - Native MCP protocol
- **VS Code + Cline** - Extension-based integration
> š **[Complete Setup Guide](docs/SETUP_GUIDE.md)** - Detailed configuration for each IDE
## š Usage Example
```text
"Use basic_auth with username 'admin' and password 'secret123'
then use auth_bypass_check on https://api.example.com/users
to test for authentication bypass vulnerabilities"
```
The AI agent will:
1. Configure authentication credentials
2. Test the protected endpoint for bypass vulnerabilities
3. Provide detailed security analysis and recommendations
## š Testing & Validation
```bash
# Comprehensive tool testing
npm run test-tools
# Manual interactive testing
npm run test-interactive
# Quick setup verification
npm run quick-start
# MCP Inspector (GUI)
npm run inspector
```
## š Project Structure
```
CyberMCP/
āāā src/ # TypeScript source code
ā āāā tools/ # 14 security testing tools
ā āāā resources/ # Security checklists & guides
ā āāā utils/ # Authentication & utilities
āāā docs/ # Documentation
āāā scripts/ # Testing & utility scripts
āāā examples/ # Configuration examples
āāā dist/ # Built JavaScript (generated)
āāā README.md # This file
```
## š§ Development
```bash
# Development mode with hot reload
npm run dev
# Build TypeScript
npm run build
# Start server (stdio mode)
npm start
# Start HTTP server
TRANSPORT=http PORT=3000 npm start
```
## š Documentation
- **[Setup Guide](docs/SETUP_GUIDE.md)** - Detailed installation and configuration
- **[Project Summary](docs/PROJECT_SUMMARY.md)** - Complete feature overview
- **[Testing Results](docs/TESTING_RESULTS.md)** - Validation and test coverage
## š¤ Contributing
1. Fork the repository
2. Create a feature branch: `git checkout -b feature/new-security-tool`
3. Make your changes and add tests
4. Submit a pull request
## š License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
## š Resources
- [Model Context Protocol](https://modelcontextprotocol.io/) - Official MCP documentation
- [OWASP API Security](https://owasp.org/www-project-api-security/) - API security best practices
- [MCP TypeScript SDK](https://github.com/modelcontextprotocol/typescript-sdk) - Development framework
---
**š Secure your APIs with AI-powered testing!**
*For support and questions, please [create an issue](https://github.com/your-username/CyberMCP/issues).* TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose focused on specific security testing or authentication functions, with no overlap between authentication methods (e.g., api_login, basic_auth, oauth2_auth) and vulnerability checks (e.g., sql_injection_check, xss_check, path_traversal_check). The tools are well-differentiated by their target areas, making misselection unlikely.
The naming follows a consistent snake_case pattern throughout, with most tools using clear descriptive names (e.g., sql_injection_check, security_headers_check). However, there are minor deviations like 'auth_bypass_check' versus 'jwt_vulnerability_check' where some use underscores more consistently than others, but overall the pattern is predictable and readable.
With 14 tools, the count is well-scoped for a cybersecurity testing server, covering a comprehensive range of authentication methods and common vulnerability checks. Each tool appears to earn its place by addressing a specific aspect of security assessment, avoiding both excessive bloat and insufficient coverage.
The tool set provides strong coverage for security testing, including authentication (e.g., api_login, basic_auth, token_auth) and vulnerability checks (e.g., sql_injection_check, xss_check). Minor gaps might exist, such as lack of tools for specific advanced attacks or reporting features, but core workflows for authentication and basic security assessments are well-covered without dead ends.