Skip to main content
Glama
Sign In
OSV-Scanner-MCP

OSV-Scanner-MCP

by tedorigawa001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to OSV-Scanner-MCP

No user-submitted related servers found.

    Related Servers

    • CVE Search MCP Server

      Arnabdaz
      F
      license
      A
      quality
      D
      maintenance
      Enables searching and analyzing CVEs and vulnerabilities from multiple sources, optimized for PR review scenarios to help developers identify the latest security issues.
      8
      2
      -

    • Risk Audit MCP

      rachellarralde
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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
      -

    • mcp-supply-chain-check

      MuellerMH
      A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to check individual project dependencies or local CycloneDX/SPDX SBOM files against the public OSV.dev advisory database and receive ranked vulnerability findings.
      2
      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

    A4/5.0

    Scored across 6 tools

    Disambiguation3/5

    scan_project, scan_java_project, and suggest_fix all perform project scanning, and scan_project already covers Java Maven/Gradle, making scan_java_project largely redundant. scan_java_artifact and scan_sbom are distinct by input type, but the boundary between generic and Java-specific project scans is fuzzy.

    Naming Consistency5/5

    All names use snake_case and follow a clear verb_noun or verb_object pattern such as scan_*, explain_*, and suggest_*. Minor ordering variation in scan_java_project versus scan_project is readable and consistent overall.

    Tool Count5/5

    Six tools is well-scoped for a vulnerability scanner and remediation server. Each tool covers a distinct input type or action without obvious bloat.

    Completeness4/5

    The core lifecycle is covered: scanning projects, Java artifacts, and SBOMs; explaining individual vulnerabilities; and suggesting fixes. Some gaps remain, such as no general non-Java artifact scanning or batch fix application, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources