What is the key difference between Osv Ui and Depscope?

Osv Ui belongs to the Security category with local stdio execution, while Depscope belongs to the Security category with local stdio execution.

How do I install Osv Ui or Depscope in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Osv Ui and Depscope free or paid?

Osv Ui operates under a Free / Open Source model (No auth required). Depscope operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Osv Ui lists 4 tools with 3 views and 4 GitHub stars. Depscope lists 22 tools with 4 views and 1 GitHub stars.

Can I use both Osv Ui and Depscope together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Osv Ui vs Depscope

In-depth architectural comparison of the Osv Ui and Depscope MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Osv Ui

Security · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Depscope

Security · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Verdict Summary: Choose Osv Ui if you need specialized Security tools running via a local process. Choose Depscope if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Osv Ui when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: scan_project, open_dashboard, get_fix_commands.

Explore Osv Ui Details

Choose Depscope when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: check_malicious, check_typosquat, check_bulk.

Explore Depscope Details

Feature & Specification Comparison

Specification	Osv Ui toan203 Security	Depscope cuttalo Security
Summary	Visual CVE audit dashboard for npm, Python, Go, and Rust. Scan from Claude/Cursor, opens a browser UI for human review (human-in-the-loop), applies fixes with explicit confirmation. Powered by OSV.dev.	Package Intelligence for AI agents. 22 tools across 17 ecosystems (npm/pypi/cargo/go/maven/nuget/rubygems/composer/pub/hex/swift/cocoapods/cpan/hackage/cran/conda/homebrew) — check health, vulnerabilities (OSV + CISA KEV + EPSS), typosquats, malicious flags, alternatives, known bugs, breaking changes, stack compatibility and error-to-fix. 31k+ packages, 2.2k+ CVEs enriched. Zero auth, MIT. Remote URL https://mcp.depscope.dev/mcp or stdio npx depscope-mcp.
Category & Scope

Tools & Capabilities Breakdown

Osv Ui Tools (4)

scan_project

Scan a project directory for CVE vulnerabilities. Automatically detects npm, Python, Go, Rust, Java/Maven, PHP/Composer, and Ruby/Bundler manifests. Queries live CVE data from OSV.dev. Returns structured vulnerability report with severity counts, risk score, and fix recommendations. Use this as the first step before open_dashboard or apply_fixes.

open_dashboard

Launch the osv-ui visual dashboard in the browser for human review. This is the HUMAN-IN-THE-LOOP step — always offer this before applying fixes. The dashboard shows full CVE details, severity charts, and the upgrade guide. Returns the dashboard URL. If already running for this path, returns existing URL.

get_fix_commands

Get the safe upgrade commands for vulnerable packages WITHOUT executing them. Use this to show the user what will be changed before calling apply_fixes. Returns a list of commands grouped by ecosystem (npm, pip, go, cargo, Maven, Composer, Bundler).

apply_fixes

Execute package upgrade commands to fix CVEs. IMPORTANT: This is a DESTRUCTIVE action that modifies package files. ALWAYS call get_fix_commands first and confirm with the user before calling this. Returns the command output for each fix applied.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Osv Ui Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "toan203-osv-ui": {
      "command": "npx",
      "args": [
        "-y",
        "osv-ui"
      ]
    }
  }
}

Depscope Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cuttalo-depscope": {
      "command": "npx",
      "args": [
        "-y",
        "depscope-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Osv Ui is categorized under Security and uses a local stdio subprocess. In contrast, Depscope belongs to Security using local stdio subprocess. Select Osv Ui when you need capabilities focused on security and Depscope when you require tools for security.

More alternatives to Osv Ui More alternatives to Depscope Security category hub Canonical compare URL