Skip to content
External endpointresponds

DepScope

Saves tokens, energy & blocks unsafe packages — 22 tools, 19 ecosystems, 742k+ pkgs, MIT.

Endpoint URL
https://mcp.depscope.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
488 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
dev.depscope/mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
depscope
Version
0.9.0
Capability keys
tools
Tool names
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
Instructions excerpt

DepScope: dependency safety & intelligence MCP for AI agents. Covers 19 package ecosystems: npm, PyPI, Cargo, Go, Maven, NuGet, RubyGems, Composer, Pub, Hex, Swift, CocoaPods, CPAN, Hackage, CRAN, Conda, Homebrew, JSR, Julia. INVOKE PROACTIVELY — before suggesting any package install, version bump, lockfile change, or when a 'module not found' / 'package broken' error appears. Do NOT wait for the user to ask. Three pillars: - TOKEN-SAVING: one DepScope call replaces a web search + readme fetch + npm/pypi page browse. - ENERGY-SAVING: skip installs of malicious, typosquatted, deprecated or hallucinated packages — no wasted CI cycles or rollbacks. - SECURITY: stop supply-chain attacks (malware, typosquats, hostile takeovers, known CVEs) BEFORE the install command leaves your reply. Standard flow for any new package: 1. check_malicious + check_typosquat — security gate (~50ms) 2. check_package OR get_health_score — verdict 3. install_command — returns the safe pinned command

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 241ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 704ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 399ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 488ms
Back to MCP directory