Skip to main content
Glama

Related Servers

Alternatives to osv-ui-mcp

Related Servers

  • 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.
    796 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories and returning unified vulnerability reports with configurable severity thresholds, dev-dependency skipping, and text or JSON output.
    5 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables auditing npm, Yarn, and pnpm lockfiles in local project directories or remote Git repositories to surface dependency vulnerabilities. Exposes a tool that supports severity thresholds, registry overrides, optional dev-dependency skipping, and text or JSON reports.
    5 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Audits npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories (public or private) and returns vulnerability reports in text or JSON. Supports configurable severity thresholds, custom npm registries, dev-dependency skipping, and report language selection.
    5 npm
    MIT
  • 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
    5 npm
    78
    MIT

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

ActivityStale
ResponsivenessNo issues