What is the key difference between Depscope and Vulnfeed Mcp?

Depscope belongs to the Security category with local stdio execution, while Vulnfeed Mcp belongs to the Security category with local stdio execution.

How do I install Depscope or Vulnfeed Mcp 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 Depscope and Vulnfeed Mcp free or paid?

Depscope operates under a Free / Open Source model (No auth required). Vulnfeed Mcp operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Depscope lists 22 tools with 3 views and 1 GitHub stars. Vulnfeed Mcp lists 9 tools with 1 views and 1 GitHub stars.

Can I use both Depscope and Vulnfeed Mcp 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.

How do I install Depscope or Vulnfeed Mcp in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Depscope and Vulnfeed Mcp free to use, or do they require API keys?

Depscope is listed under a Free / Open Source model with No auth required . Vulnfeed Mcp operates under a Freemium model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Depscope and Vulnfeed Mcp at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both cuttalo-depscope and infai-tech-vulnfeed-mcp as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Depscope has a Quality Score of 60 /100 ( Good ) with 3 views, 0 installs, and 1 GitHub stars. Vulnfeed Mcp holds a Quality Score of 57 /100 ( Good ) with 1 views, 0 installs, and 1 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Depscope vs Vulnfeed Mcp

In-depth architectural comparison of the Depscope and Vulnfeed Mcp 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

Depscope

Security · Local stdio

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

Vulnfeed Mcp

Security · Local stdio

Quality: 57/100 (Good) | Auth: API Key required

Verdict Summary: Choose Depscope if you need specialized Security tools running via a local process. Choose Vulnfeed Mcp 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 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

Choose Vulnfeed Mcp when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: VULNFEED_API_KEY.
Primary tools included: scan_project, scan_lockfile, check_package.

Explore Vulnfeed Mcp Details

Feature & Specification Comparison

Specification	Depscope cuttalo Security	Vulnfeed Mcp infai-tech Security
Summary	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.	Dependency vulnerability scanner with EPSS exploit probability scoring. Scans lockfiles (npm, pip, Go, Cargo, Ruby, Composer, Gradle, NuGet, Mix), prioritizes by real-world exploit likelihood, recommends fix versions. 9 MCP tools for scanning, monitoring, and alerting. Free tier + x402 micropayments. pip install vulnfeed-mcp

Tools & Capabilities Breakdown

Depscope Tools (22)

check_malicious

Supply-chain malware check against OpenSSF/OSV. USE WHEN: about to suggest install of an unvetted/unfamiliar package; name came from a blog/tutorial. Call BEFORE check_package for untrusted pkgs. RETURNS: {is_malicious, threat_tier, source}.

check_typosquat

Typosquat detector. USE WHEN: name differs from a well-known package by 1-2 chars (`lodsh`, `reqeusts`); copy-paste from unreliable source; downloads near zero but name looks familiar. RETURNS: {is_typosquat, likely_target, confidence}.

check_bulk

Fast pre-flight filter for a batch of (ecosystem, package) pairs. DB-only, <100ms for 100 items. USE WHEN: about to emit `npm install a b c …` or `pip install a b c …` — catches hallucinated names, stdlib, typos, and known-bad in ONE call. NOT a dep-tree audit (use scan_project for that). RETURNS: per-item {status: exists|stdlib|malicious|typosquat_suspect|historical_incident|unknown}.

package_exists

Boolean registry existence check. USE WHEN: about to emit a package name in an install command but unsure it exists; verifying a name generated from training data. RETURNS: {exists}.

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).

Depscope Configuration

mcpServers (Claude Desktop / Cursor)

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

Vulnfeed Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "infai-tech-vulnfeed-mcp": {
      "command": "uvx",
      "args": [
        "vulnfeed-mcp"
      ],
      "env": {
        "VULNFEED_API_KEY": "YOUR_VULNFEED_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Depscope More alternatives to Vulnfeed Mcp Security category hub