Skip to main content
Glama
toan203

osv-ui-mcp

by toan203
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to osv-ui-mcp

Related Servers

  • @guardbee/mcp-dependency-auditor by GuardBee

    @guardbee/mcp-dependencyofficial

    GuardBee
    A
    license
    Not graded
    quality
    F
    maintenance
    Enables auditing npm, pip, and other package dependencies for known CVEs via the OSV database, with tools to scan manifests, query individual packages, and integrate into CI/CD workflows.
    99 npm
    MIT

  • locklens

    BARMPlus
    A
    license
    B
    quality
    D
    maintenance
    Audits package lockfiles for vulnerabilities, supporting npm, yarn, and pnpm. Runs via CLI or as an MCP server over stdio.
    1
    1 npm
    83
    MIT

  • GuardianMCP

    Kalvisan
    A
    license
    A
    quality
    C
    maintenance
    Automatically scans project dependencies (npm, Composer) for security vulnerabilities using the OSV.dev database, providing real-time alerts and detailed remediation guidance directly in your IDE.
    1
    6 npm
    1
    MIT
  • Git-Fabric CVE by git-fabric

    Git-Fabric CVEofficial

    git-fabric
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    Provides tools for autonomous CVE detection, enrichment, and remediation across managed repositories using GHSA and NVD data. It enables automated triage and pull request creation for dependency fixes based on configurable severity policies.
    -

  • DepsGuard MCP

    Kim-Kyowon
    A
    license
    A
    quality
    D
    maintenance
    AI-powered dependency vulnerability and breaking change analyzer that scans dependencies, identifies vulnerabilities via OSV.dev, and uses AI to assess real impact and suggest fixes.
    3
    Apache 2.0
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/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct phase in the workflow: scanning, dashboard review, previewing fix commands, and executing fixes. There is no meaningful overlap between the tools.

Naming Consistency5/5

All tool names follow the same snake_case verb_noun pattern: scan_project, open_dashboard, get_fix_commands, apply_fixes. The naming is predictable and clearly signals the action being performed.

Tool Count5/5

Four tools is well-scoped for a focused vulnerability scanning and remediation workflow. Each tool serves a necessary step with no redundant or extraneous tools.

Completeness5/5

The tools cover the full lifecycle from scanning a project, reviewing results in the dashboard, previewing safe fix commands, and applying fixes. No obvious gaps exist for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources