package_exists — DepScope MCP Tool
package_exists
(package exists) is one of 22 tools on the
DepScope
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call package_exists from your client
- Claude Code DepScope package_exists run in your project directory
- Claude Desktop DepScope package_exists ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DepScope package_exists ~/.cursor/mcp.json
- VS Code DepScope package_exists .vscode/mcp.json
- Zed DepScope package_exists ~/.config/zed/settings.json
- Windsurf DepScope package_exists ~/.codeium/windsurf/mcp_config.json
- Cline DepScope package_exists ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DepScope package_exists ~/.gemini/settings.json
- Grok DepScope package_exists .mcp.json (in your project root)
- ChatGPT DepScope package_exists Settings → Connectors → Advanced → Developer mode
- Claude.ai DepScope package_exists Settings → Connectors → Add custom connector
- LangChain DepScope package_exists pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.depscope.dev/mcpOther tools on this server
- check_malicious
- check_typosquat
- check_bulk
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.