CyberMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Authentication Security Checklist | Security checklist for authentication vulnerabilities |
| Injection Security Checklist | Security checklist for injection vulnerabilities |
| Data leakage Security Checklist | Security checklist for data leakage vulnerabilities |
| Rate limiting Security Checklist | Security checklist for rate limiting vulnerabilities |
| General Security Checklist | Security checklist for general vulnerabilities |
| Jwt testing Testing Guide | Comprehensive guide for testing jwt testing vulnerabilities |
| Auth bypass Testing Guide | Comprehensive guide for testing auth bypass vulnerabilities |
| Sql injection Testing Guide | Comprehensive guide for testing sql injection vulnerabilities |
| Xss Testing Guide | Comprehensive guide for testing xss vulnerabilities |
| Rate limiting Testing Guide | Comprehensive guide for testing rate limiting vulnerabilities |
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.