DevSecOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAP_URL | No | URL for OWASP ZAP API (required if using ZAP in API mode; default is Docker) | |
| MCP_PORT | No | Port for the MCP server | 3000 |
| NODE_ENV | No | Environment mode (e.g., production, development) | production |
| LOG_LEVEL | No | Logging level (info, debug, warn, error) | info |
| TRIVY_PATH | No | Path to the Trivy executable | trivy |
| ZAP_API_KEY | No | API key for OWASP ZAP authentication | |
| SONARQUBE_URL | No | URL for SonarQube server (required for SonarQube integration) | |
| SONARQUBE_TOKEN | No | Authentication token for SonarQube | |
| TRIVY_CACHE_DIR | No | Directory for Trivy scan cache | /tmp/trivy-cache |
| OSV_SCANNER_PATH | No | Path to the OSV Scanner executable | osv-scanner |
| SECURITY_STRICT_MODE | No | Enable strict security mode | true |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_sast_scanC | Execute SAST (Static Application Security Testing) scan |
| run_dast_scanC | Execute DAST (Dynamic Application Security Testing) scan |
| run_sca_scanC | Execute SCA (Software Composition Analysis) scan |
| run_iast_scanC | Execute IAST (Runtime Configuration & Header Analysis) scan |
| generate_security_reportC | Generate comprehensive security report from all scans |
| validate_security_policyC | Validate security policy compliance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting specific security scanning types or report generation, with no overlap in functionality. The descriptions clearly differentiate between DAST, IAST, SAST, SCA scans, report generation, and policy validation.
All tools follow a consistent verb_noun pattern with 'run_' or 'generate_'/'validate_' prefixes followed by specific security terms. The naming is perfectly uniform across all six tools, making them easily predictable and readable.
Six tools is well-scoped for a DevSecOps security scanning server, covering the major scanning types (DAST, IAST, SAST, SCA), report generation, and policy validation. Each tool earns its place without being excessive or insufficient.
The toolset provides comprehensive coverage of core security scanning operations and reporting for a DevSecOps domain. Minor gaps might include tools for managing scan configurations or viewing historical results, but the current set supports essential workflows effectively.