McpServer

CervantesSec/McpServer

3.2

If you are the rightful owner of McpServer and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The MCP Server for Cervantes is a .NET-based implementation that integrates with the Cervantes penetration testing management platform, enabling AI assistants to interact with Cervantes data through the Model Context Protocol.

Tools
  1. ClientTool

    Manage client information and avatars.

  2. ProjectTool

    Handle projects, members, notes, and attachments.

  3. VulnerabilityTool

    Complete vulnerability lifecycle management.

  4. TaskTool

    Task management with notes, targets, and attachments.

  5. ReportTool

    Report generation and template management.

  6. DocumentTool

    Document management and organization.

  7. VaultTool

    Secure credential and sensitive data storage.

  8. NoteTool

    General note-taking and organization.

  9. UserTool

    User and role management.

  10. RoleTool

    Permission and access control management.

MCP Server for Cervantes

.NET MCP

A Model Context Protocol (MCP) server implementation that provides seamless integration with the Cervantes penetration testing management platform API. This server enables AI assistants like Claude to interact with Cervantes data through standardized MCP tools.

šŸŽÆ Purpose

This MCP server acts as a bridge between AI assistants and the Cervantes platform, allowing users to:

  • Manage penetration testing projects, clients, and tasks through natural language
  • Query and manipulate vulnerability data
  • Generate reports and manage documentation
  • Handle user and role management
  • Interact with vault and notes systems

šŸ›  Technologies

  • .NET 9.0 - Core framework
  • Model Context Protocol - Communication standard
  • HTTP Client - REST API integration
  • Dependency Injection - Service management

✨ Features

šŸ“‹ Project Management

  • Create, read, update, and delete projects
  • Manage project members and permissions
  • Handle project notes and attachments
  • Generate executive summaries

šŸ” Vulnerability Management

  • Complete CRUD operations for vulnerabilities
  • Vulnerability categorization and CWE mapping
  • Risk assessment and status tracking
  • Notes, targets, and attachments management
  • Template system support

šŸ‘„ Client Management

  • Client information management
  • Avatar upload support
  • Project association

šŸ“ Task Management

  • Task creation and assignment
  • Status tracking and updates
  • Notes and attachments support
  • Target association

šŸ“Š Reporting

  • Report generation and management
  • Template system
  • Component management
  • Multiple export formats

šŸ” Security & Access

  • User and role management
  • Vault for secure credential storage
  • Permission-based access control

šŸ“„ Documentation

  • Document management system
  • File upload and organization
  • Version control support

šŸ”§ Runtime Requirements

  • .NET 9.0 Runtime or later
  • Cervantes instance (running and accessible)
  • Network connectivity to Cervantes API endpoints

šŸ“¦ Installation

From Source

  1. Clone the repository

    git clone https://github.com/CervantesSec/McpServer.git
    cd mcpserver-cervantes
    
  2. Build the project

    dotnet build --configuration Release
    
  3. Run the server

    dotnet run --project McpServer
    

āš™ļø Configuration

appsettings.json

Configure the server by modifying the appsettings.json file:

{
  "Cervantes": {
    "BaseUrl": "https://your-cervantes-instance.com",
    "Username": "your-username",
    "Password": "your-password",
    "AuthMethod": "BasicAuth"
  },
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning"
    }
  }
}

Environment Variables (Alternative)

You can also configure using environment variables:

# Cervantes API Configuration
CERVANTES__BASEURL=https://your-cervantes-instance.com
CERVANTES__USERNAME=your-username
CERVANTES__PASSWORD=your-password
CERVANTES__AUTHMETHOD=BasicAuth

# Logging Configuration
LOGGING__LOGLEVEL__DEFAULT=Information

MCP Integration

Add the server to your MCP client configuration:

{
  "servers": {
    "cervantes": {
      "command": "dotnet",
      "args": ["run", "--project", "/path/to/McpServer"],
      "env": {
        "CERVANTES_API_BASE_URL": "https://your-cervantes-instance.com"
      }
    }
  }
}

šŸš€ Usage

Once configured, the MCP server provides the following tool categories:

Available Tools

  • ClientTool: Manage client information and avatars
  • ProjectTool: Handle projects, members, notes, and attachments
  • VulnerabilityTool: Complete vulnerability lifecycle management
  • TaskTool: Task management with notes, targets, and attachments
  • ReportTool: Report generation and template management
  • DocumentTool: Document management and organization
  • VaultTool: Secure credential and sensitive data storage
  • NoteTool: General note-taking and organization
  • UserTool: User and role management
  • RoleTool: Permission and access control management

Example Usage with Claude

"Can you show me all high-risk vulnerabilities in the current project?"

"Create a new client named 'Acme Corp' with contact email admin@acme.com"

"Generate a penetration testing report for project ID abc-123"

šŸ¤ How to Contribute

We welcome contributions! Here's how you can help:

  1. Fork the repository
  2. Create a feature branch
    git checkout -b feature/amazing-feature
    
  3. Make your changes and add tests
  4. Commit your changes
    git commit -m 'Add amazing feature'
    
  5. Push to your branch
    git push origin feature/amazing-feature
    
  6. Open a Pull Request

Development Guidelines

  • Follow C# coding conventions
  • Add unit tests for new features
  • Update documentation as needed
  • Ensure all builds pass
  • Use meaningful commit messages

šŸ”’ Security

If you discover a security vulnerability, please send an email to . All security vulnerabilities will be promptly addressed.

Security Features

  • Secure API communication
  • Input validation and sanitization
  • Error handling without information disclosure
  • Structured logging for audit trails

šŸ› How to Report Bugs

If you find a bug, please create an issue on GitHub with:

  • Clear description of the problem
  • Steps to reproduce
  • Expected vs actual behavior
  • Environment details (.NET version, OS, etc.)
  • Relevant logs or error messages

šŸ“š Documentation

šŸ—ļø Architecture

The server follows a modular architecture:

McpServer/
ā”œā”€ā”€ Models/          # Data models and ViewModels
ā”œā”€ā”€ Services/        # API client and business logic
ā”œā”€ā”€ Tools/           # MCP tool implementations
└── Program.cs       # Application entry point

Key Components

  • CervantesApiClient: HTTP client for API communication
  • Tool Classes: Individual MCP tool implementations
  • Model Classes: Data transfer objects and ViewModels
  • Dependency Injection: Service registration and lifetime management

šŸ”„ API Coverage

The server provides comprehensive coverage of the Cervantes API:

  • āœ… Client Management
  • āœ… Project Management
  • āœ… Vulnerability Management
  • āœ… Task Management
  • āœ… Report Generation
  • āœ… Document Management
  • āœ… User & Role Management
  • āœ… Vault Management
  • āœ… Notes System

šŸ“Š Supported Operations

ResourceCreateReadUpdateDeleteSpecial Operations
Clientsāœ…āœ…āœ…āœ…
Projectsāœ…āœ…āœ…āœ…Members, notes, attachments
Vulnerabilitiesāœ…āœ…āœ…āœ…Templates, categories, CWE
Tasksāœ…āœ…āœ…āœ…Notes, targets, attachments
Reportsāœ…āœ…āœ…āœ…Templates, components, generation
Documentsāœ…āœ…āœ…āœ…Doc management
Vaultāœ…āœ…āœ…āœ…
Usersāœ…āœ…āœ…āœ…Role assignment

šŸ“ˆ Performance

  • Async/await throughout for optimal performance
  • Connection pooling for HTTP requests
  • Structured logging for observability
  • Graceful error handling and recovery

šŸ“ License

This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0) - see the file for details.

AGPL-3.0 License Summary

The AGPL-3.0 license ensures that:

  • āœ… You can use, modify, and distribute this software freely
  • āœ… You must provide source code for any modifications
  • āœ… Network use is considered distribution - if you run this server for others to access, you must provide the source code
  • āœ… Any derivative works must also be licensed under AGPL-3.0
  • āœ… You must include copyright and license notices

This license is specifically chosen to ensure that improvements to this MCP server remain open source, even when deployed as a service.

šŸ™ Acknowledgments

  • CervantesSec for the excellent penetration testing platform
  • Anthropic for the Model Context Protocol specification
  • The .NET community for excellent tooling and libraries

šŸ“ž Support


Made with ā¤ļø for the cybersecurity community