OSV-Scanner-MCP
Related Servers
Alternatives to OSV-Scanner-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables scanning Java/Maven projects to generate TOGAF-standard architecture deliverables (Excel and PPTX) via natural language commands.6MIT
- FlicenseAqualityDmaintenanceEnables searching and analyzing CVEs and vulnerabilities from multiple sources, optimized for PR review scenarios to help developers identify the latest security issues.82-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables security scanning of code projects to identify common vulnerabilities like XSS, injections, SSRF, and path traversal issues. Provides local, offline scanning with severity-grouped results and actionable fix suggestions for improving code security.38 npm-
- AlicenseNot gradedqualityDmaintenanceEnables scanning projects for dependency vulnerabilities, secrets, license conflicts, code quality, and git health, returning a 0-100 health score with actionable suggestions.1 npmMIT
- FlicenseNot gradedqualityCmaintenanceScans Python, Node.js, Java/Spring, and PHP dependency manifests for known vulnerabilities using OSV and GitHub Advisory APIs.-
- AlicenseBqualityDmaintenanceEnables searching Maven Central artifacts, retrieving versions, and analyzing dependencies via natural language.5MIT
TDQS
Scored across 5 tools
Most tools have clear boundaries: scan_java_project, scan_java_artifact, scan_sbom, explain_vulnerability, and suggest_fix each have distinct primary purposes. However, suggest_fix also scans a Java project and surfaces vulnerability/fix-version details, so it could be confused with scan_java_project when an agent simply wants a vulnerability scan.
All tool names follow a consistent imperative verb_noun pattern with snake_case: scan_java_project, scan_java_artifact, scan_sbom, explain_vulnerability, and suggest_fix. The naming convention is uniform and predictable.
Five tools is a well-scoped set for this server's purpose. Each tool covers a distinct operation: scanning projects, scanning artifacts, scanning SBOMs, explaining vulnerabilities, and suggesting fixes. No tool feels redundant or unnecessary.
The tool surface covers the main vulnerability workflow well: scanning multiple input types, explaining findings, and recommending upgrade paths. Minor gaps exist, such as fix suggestions being limited to Java project scans and no direct support for non-Java package manifests.