dev.depscope/mcp — Model Context Protocol (MCP) server

Package intelligence MCP server for AI agents. It provides tooling to prevent AI coding agents (including Claude, ChatGPT, Cursor, Windsurf, and Copilot) from installing hallucinated, deprecated, or malicious packages. Coverage is across 19 ecosystems, with 22 tools exposed via MCP. It is provided under an AGPL-3.0 license.

🛠️ Key Features

MCP-compatible package intelligence
22 tools
Scans/guards against hallucinated, deprecated, and malicious packages
Targets 19 ecosystems
Focus areas include supply-chain security and slopsquatting
Topics include vulnerability scanning and model-context-protocol

🚀 Use Cases

Use by AI coding agents to reduce risk during dependency installation
Supply-chain security checks across multiple package ecosystems
Vulnerability scanner workflows related to package sources

⚡ Developer Benefits

Model Context Protocol integration for AI agents
Package-manager ecosystem coverage (npm, PyPI, Cargo and others implied by “19 ecosystems”)
Developer-oriented focus via “mcp-server”, “security”, and “supply-chain-security” topics

⚠️ Limitations

Described scope is package integrity prevention across 19 ecosystems (specific ecosystems/tool behavior beyond this is not detailed in the provided excerpt)

DepScope MCP Server

Package intelligence MCP server for AI agents. Stops AI coding agents (Claude, ChatGPT, Cursor, Windsurf, Copilot) from installing hallucinated, deprecated, or malicious packages across 19 ecosystems.

→ Backed by depscope.dev — 1.2M+ packages indexed, 19,000+ vulnerabilities tracked, real-time.

What's new in v0.9.0

The MCP server now sends a system-prompt directive to your AI client at handshake (server.instructions). Claude Code, Cursor, Windsurf and other MCP clients receive a proactive-invocation brief automatically — manual rule files (CLAUDE.md, .cursorrules, .windsurfrules) are now optional. Existing rules still work; they're just redundant.

What the model sees at every session start:

The 19-ecosystem coverage list
An "INVOKE PROACTIVELY" directive with explicit triggers (install, version bump, lockfile change, "module not found" errors, library comparison)
Three pillars: token-saving, energy-saving, security
Standard invocation flow: check_malicious → check_typosquat → check_package → install_command

For Claude Code there is also a companion plugin that bundles the MCP server with a skill carrying rich frontmatter triggers:

bash

git clone https://github.com/cuttalo/depscope-claude-plugin ~/.claude/plugins/depscope

All npm versions <0.9.0 are now deprecated. Run npm update -g depscope-mcp if you installed globally.

Why this exists

LLMs frequently invent package names that look real but don't exist (fastapi-turbo, lodahs, tokio-stream-extras). When an agent tries to install one, it might hit an attacker's typosquat. DepScope verifies every package before install.

Quick start

Claude Desktop / Cursor / Windsurf (remote MCP)

Add to your MCP config:

json

{
  "mcpServers": {
    "depscope": {
      "url": "https://mcp.depscope.dev/mcp"
    }
  }
}

Local (stdio via npx)

json

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

Tools (22)

Tool	Purpose
`check_package`	Full package check: deprecated/CVE/health/recommendation
`get_health_score`	0-100 score with breakdown (maintenance/popularity/security/maturity/community)
`get_vulnerabilities`	Open CVEs from OSV + KEV/EPSS
`package_exists`	Hallucination detector (404 = LLM invented it)
`find_alternatives`	Curated alternatives for deprecated/abandoned packages
`get_typosquat`	Suspicious name similarity check
`get_breaking_changes`	Migration plan between versions
`get_bugs`	Known bugs from GitHub issues
`compare_packages`	Side-by-side health/license/vuln comparison
`resolve_error`	Map error message → likely cause + fix
`search_errors`	Find similar error reports across ecosystems
`check_compat`	Stack compatibility check
`get_latest_version`	Latest stable + maturity signal
... and 9 more	full list in `tools.js`

Ecosystems (19)

npm · pypi · cargo · go · composer · maven · nuget · rubygems · pub · hex · swift · cocoapods · cpan · hackage · cran · conda · homebrew · jsr · julia

Pricing

Free. No auth required. Generous rate limits. The MCP server is open-source (AGPL-3.0); the backend (depscope.dev API) is proprietary.

License

AGPL-3.0-or-later. Backend is proprietary; this client is open.

ecosystem	string	required
from_package	string	required	Deprecated/legacy package to migrate away from.
to_package	string	required	Modern replacement package.

ecosystem	string	required
package	string	required
min_severity	string	optional	Lowest severity to exclude. Default: high (excludes critical+high).
constraint	string	optional	npm-style constraint: ^X.Y.Z, ~X.Y.Z, >=X.Y.Z, or exact X.Y.Z.
include_prerelease	boolean	optional

error	string	optional	Concrete error message / stack trace. Triggers exact-match lookup.
query	string	optional	Free-text symptom description. Triggers KB search.
context	object	optional	Optional context for error-mode calls (ecosystem, package, version).
limit	integer	optional	Max search results (query mode only).

kind	string	optional	Ticket category. `anomaly` routes to structured anomaly triage (requires tool_called/observed/expected).
email	string	optional	Reply-to email of the requester (required for bug/listing/security/partnership).
subject	string	optional	Short subject line (3-200 chars).
body	string	optional	Message body (10-8000 chars). Be specific: include package name, ecosystem, error trace, repro steps when applicable.
name	string	optional	Sender display name (optional).
company	string	optional	Company / organization (optional).
tool_called	string	optional	For kind=anomaly: DepScope tool that produced the anomaly (e.g. check_package, get_migration_path).
ecosystem	string	optional	For kind=anomaly: ecosystem of the involved package, if any.
package	string	optional	For kind=anomaly: package name involved, if any.
version	string	optional	For kind=anomaly: package version involved, if any.
observed	string	optional	For kind=anomaly: what DepScope returned (1-1500 chars).
expected	string	optional	For kind=anomaly: what you expected to see (1-1500 chars). Be concrete.
evidence_url	string	optional	For kind=anomaly: URL to authoritative source (registry page, GHSA, CVE, repo, ...) supporting your expectation.

ecosystem	string	optional	Required when packages is a string array.
packages	any	required	Either ['express','lodash@4.17.0'] (single ecosystem, up to 100) or [{ecosystem, package}, …] (mixed, up to 50).

ecosystem	string	optional	Optional. If omitted returns cross-ecosystem trending.
scope	string	optional	Time window. Defaults to week.
limit	integer	optional	Max results, 1-50. Default 20.

dev.depscope/mcp — Model Context Protocol (MCP) server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

check_malicious

check_typosquat

check_bulk

package_exists

get_latest_version

get_health_score

install_command

get_package_prompt

check_package

get_vulnerabilities

find_alternatives

get_migration_path

get_breaking_changes

pin_safe

scan_project

compare_packages

check_compatibility

resolve_error

get_known_bugs

get_trust_signals

get_trending

contact_depscope