Skip to main content
Glama
inspicere

mcp-defectdojo

by inspicere
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-defectdojo

No user-submitted related servers found.

    Related Servers

    • DefectDojo MCP Server

      jamiesonio
      A
      license
      B
      quality
      D
      maintenance
      Provides a Model Context Protocol server implementation that allows AI agents and other MCP clients to programmatically interact with DefectDojo, a vulnerability management tool, for managing findings, products, and engagements.
      11
      63 PyPI
      16
      MIT

    • va-pentest-mcp

      banhongit7
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for automated security vulnerability assessment, combining OWASP Dependency-Check dependency scanning with custom code vulnerability detection, and generating detailed HTML and JSON reports.
      -

    • offsec-mcp

      nadirzhon
      A
      license
      A
      quality
      B
      maintenance
      MCP server for offensive-security tooling, enabling AI agents to run reconnaissance, CVE intelligence, JavaScript analysis, HTTP probing, and port scanning against authorized targets.
      10
      MIT

    • ZAP MCP Proxy

      madmystic
      F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that wraps OWASP ZAP's REST API as Model Context Protocol tools, enabling AI agents to perform automated security scanning.
      -

    • reptor-mcp

      slvnlrt
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes the pentest reporting and automation features of SysReptor as programmable tools for AI agents and automated workflows. It enables users to manage findings, projects, and templates through a standardized interface by wrapping the reptor CLI.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct entity and action (e.g., product, engagement, test, finding, tags, scans). Detailed descriptions and unique argument sets prevent confusion. No two tools overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., create_product, list_findings, close_finding). Even health_check fits the pattern. No mixing of styles or ambiguous verbs.

    Tool Count4/5

    24 tools is slightly above the ideal range but still reasonable given the breadth of DefectDojo's API (products, engagements, tests, findings, notes, tags, scans). Each tool serves a clear need; no superfluous tools.

    Completeness3/5

    The toolset covers CRUD for findings and basic operations for products, engagements, and tests. However, missing update endpoints for product and engagement, and no delete operations anywhere, which are notable gaps for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources