About DepScope
DepScope is a package-intelligence MCP server for coding agents, checking dependencies across 19 ecosystems before installation. It combines package existence, security, maintenance, compatibility, and migration information in 22 tools.
Key features
- 01Package existence and risk checks
- 02Vulnerability and health scoring
- 03Typosquat detection
- 04Version changes and alternatives
- 05Error diagnosis and stack compatibility
Use cases
- 01Verify a package before installing it
- 02Compare dependency health and vulnerabilities
- 03Find replacements for abandoned packages
- 04Diagnose dependency errors
MCP support
Exposes 22 package-intelligence tools to MCP clients. It provides a remote endpoint and a local stdio option, and sends invocation guidance during the MCP handshake.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.depscope.dev/mcpclaude mcp add --transport http dev-depscope https://mcp.depscope.dev/mcp{"mcpServers":{"dev-depscope":{"type":"http","url":"https://mcp.depscope.dev/mcp"}}}Open in Cursor{"servers":{"dev-depscope":{"type":"http","url":"https://mcp.depscope.dev/mcp"}}}Open in VS Code{"mcpServers":{"dev-depscope":{"type":"http","url":"https://mcp.depscope.dev/mcp"}}}{"mcpServers":{"dev-depscope":{"serverUrl":"https://mcp.depscope.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEDepScope 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:
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:
{
"mcpServers": {
"depscope": {
"url": "https://mcp.depscope.dev/mcp"
}
}
}
Local (stdio via npx)
{
"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.
Links
- depscope.dev — homepage
- docs — integration guide
- Glama listing
- awesome-mcp-servers
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.