DepScope
DepScope
Аналитика пакетов для ИИ-агентов. Предотвращает установку ИИ-агентами (Claude, ChatGPT, Cursor, Windsurf, Copilot, Cline) галлюцинированных, устаревших или вредоносных пакетов в 19 экосистемах.
→ Работает на depscope.dev · 8.4 млн+ пакетов · 42 тыс.+ уязвимостей (99% с данными EPSS) · без авторизации · бесплатно
Быстрый старт (MCP)
Claude Desktop / Cursor / Windsurf — удаленно
{
"mcpServers": {
"depscope": {
"url": "https://mcp.depscope.dev/mcp"
}
}
}Claude Code / локально — stdio
{
"mcpServers": {
"depscope": {
"command": "npx",
"args": ["-y", "depscope-mcp"]
}
}
}Исходный код MCP-сервера находится по адресу cuttalo/depscope-mcp (AGPL-3.0).
Related MCP server: mcp-dep-tools
Что он делает
22 MCP-инструмента для 19 экосистем пакетов:
npm · pypi · cargo · go · composer · maven · nuget · rubygems · pub · hex · swift · cocoapods · cpan · hackage · cran · conda · homebrew · jsr · julia
Инструмент | Назначение |
| Полная проверка безопасности: устаревание · уязвимости · состояние · рекомендации |
| Детектор вредоносных пакетов |
| Обнаружение тайпосквоттинга в сравнении с популярными именами |
| Детектор галлюцинаций (404 = LLM выдумала его) |
| Оценка состояния 0–100 с детализацией |
| Уязвимости + оценка серьезности |
| Предлагаемые альтернативы для устаревших/заброшенных пакетов |
| Заметки о миграции между мажорными версиями |
| Известные проблемы пакета |
| Сравнение пакетов бок о бок |
| Проверка совместимости на уровне стека |
| Сообщение об ошибке → вероятная причина + исправление |
| Проверенная команда установки для целевой экосистемы |
| Последняя стабильная версия + сигнал зрелости |
| Предлагаемая безопасная фиксация версии |
| Оценка доверия на основе нескольких сигналов |
| Пошаговый план обновления |
| Массовое сканирование манифестов зависимостей |
| Быстрый предварительный фильтр для пакетов |
| Трендовые пакеты по экосистемам |
| Компактная сводка для LLM |
| Сообщить об отсутствующем пакете или ложном срабатывании |
REST API
Те же данные, обычный HTTPS — клиент MCP не требуется.
curl https://depscope.dev/api/check/npm/lodash
curl https://depscope.dev/api/check/pypi/requests
curl https://depscope.dev/api/check/cargo/serdeПолная документация: depscope.dev/integrate
Зачем это нужно
LLM часто придумывают имена пакетов, которые выглядят настоящими, но не существуют (fastapi-turbo, lodahs, tokio-stream-extras). Когда агент пытается установить такой пакет, он может попасть на тайпосквоттинг злоумышленника. DepScope проверяет каждый пакет перед установкой.
Подробнее: depscope.dev/why
Стоимость
Бесплатно. Авторизация не требуется. Щедрые лимиты запросов.
Если вам нужны более высокие квоты, SLA или развертывание on-prem, свяжитесь с нами по адресу depscope@cuttalo.com.
Open source vs проприетарное ПО
Этот репозиторий является только лендингом с документацией.
MCP-сервер (клиентский SDK) — open source, AGPL-3.0: → cuttalo/depscope-mcp → npm: depscope-mcp
Бэкенд (API + уровень аналитики) — проприетарный, размещен на
depscope.dev.
Такое разделение позволяет нам сохранять клиент бесплатным, проверяемым и расширяемым сообществом, поддерживая при этом инфраструктуру, которая обеспечивает его работу.
Ссылки
Домашняя страница · depscope.dev
Документация API · depscope.dev/integrate
Исходный код MCP-сервера · cuttalo/depscope-mcp
npm · depscope-mcp
Листинг Glama · glama.ai/mcp/servers/cuttalo/depscope
Awesome MCP · punkpeye/awesome-mcp-servers
Лицензия
Этот README и сопутствующие файлы лендинга: CC-BY-4.0. Клиентский SDK MCP: AGPL-3.0 (см. cuttalo/depscope-mcp). Сервис бэкенда: проприетарный.
Создано Cuttalo srl · Италия 🇮🇹
Available Tools
22 toolscheck_bulkARead-onlyIdempotentInspect
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}.
Inputs: items (required).
check_compatibilityARead-onlyIdempotentInspect
Is this specific multi-package version combo verified to work together? USE WHEN: pinning a stack (next@15 + react@19 + node@22); before recommending a version matrix. RETURNS: {compatible, conflicts[], notes}.
Inputs: packages (required).
check_maliciousARead-onlyIdempotentInspect
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}.
Inputs: ecosystem (required), package (required).
check_packageARead-onlyIdempotentInspect
Full machine-readable JSON report (~2k tokens). USE WHEN: you need to programmatically parse specific fields (CI gating, UI, sub-field extraction). Otherwise prefer get_package_prompt. RETURNS: {package, health:{score}, vulnerabilities[], latest, deprecated, maintainers, recommendation}.
Inputs: ecosystem (required), package (required), version.
check_typosquatARead-onlyIdempotentInspect
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}.
Inputs: ecosystem (required), package (required).
compare_packagesARead-onlyIdempotentInspect
Side-by-side comparison (health, vulns, downloads, maintainers, last release) of 2-10 packages in the same ecosystem. USE WHEN: 'X vs Y' / 'should I pick X or Y'. RETURNS: table-shaped JSON, one row per package.
Inputs: ecosystem (required), packages (required).
contact_depscopeAInspect
Inbound ticket: bug/listing/security/anomaly/partnership. USE WHEN: reporting wrong data (bug), requesting a new pkg/ecosystem index (listing), disclosing a DepScope security issue (security), flagging a concrete mismatch in another tool's output vs. authoritative source (anomaly — provide tool_called+observed+expected), or partnership/press (partnership). RETURNS: {ticket_id} or {anomaly_id}.
Inputs: kind, email, subject, body, +9 more.
find_alternativesARead-onlyIdempotentInspect
Curated replacements for deprecated/unhealthy packages, including stdlib built-ins (e.g. fs.rm for rimraf). USE WHEN: pkg flagged AVOID/URGENT; 'what to use instead of X'; before guessing a replacement name. RETURNS: {alternatives[]: {name, reason, is_stdlib}}.
Inputs: ecosystem (required), package (required).
get_breaking_changesARead-onlyIdempotentInspect
Breaking changes between two majors of the SAME package (next@14→15). USE WHEN: user is bumping a major; before recommending a major upgrade. Different from get_migration_path (same pkg vs. different pkg). RETURNS: {breaking_changes[]: {area, description, hint}}.
Inputs: ecosystem (required), package (required), from_version, to_version.
get_health_scoreARead-onlyIdempotentInspect
Single 0-100 health score — cheapest go/no-go gate (>=70 safe). USE WHEN: CI gating or pkg already screened for malware/typos. NOT a first screen — run check_malicious + check_typosquat first. For a verbal verdict use get_package_prompt. RETURNS: {score, verdict}.
Inputs: ecosystem (required), package (required).
get_known_bugsARead-onlyIdempotentInspect
Non-CVE known bugs for a specific package version. USE WHEN: unexpected behavior that is NOT a security issue; a pinned version misbehaves. RETURNS: {bugs[]: {title, fixed_in, workaround}}.
Inputs: ecosystem (required), package (required), version.
get_latest_versionARead-onlyIdempotentInspect
Latest published version + deprecation flag — the cheapest call. USE WHEN: only a version string matters (pinning a dep, answering 'what version of X'). If you also need health/vulns use check_package. RETURNS: {latest, deprecated, published_at}.
Inputs: ecosystem (required), package (required).
get_migration_pathARead-onlyIdempotentInspect
Prescriptive migration plan between DIFFERENT packages — rationale + literal code diff + breaking changes + effort minutes. USE WHEN: replacing request→axios, moment→dayjs, flask→fastapi, etc.; both endpoints known. RETURNS: {rationale, diff, breaking_changes[], estimated_minutes}.
Inputs: ecosystem (required), from_package (required), to_package (required).
get_package_promptARead-onlyIdempotentInspect
LLM-optimised package brief — plain text ~300 tokens (~75% cheaper than JSON). Verdict (SAFE/AVOID/URGENT/MALICIOUS) + health + vulns + alternatives + maintainer alerts. USE WHEN: you want to reason over a package and drop the output directly in context; 'is X safe'. PREFER THIS over check_package in 95% of LLM cases. RETURNS: plain-text brief.
Inputs: ecosystem (required), package (required).
get_trendingARead-onlyIdempotentInspect
Live trending packages with rank-delta and weekly growth %. USE WHEN: 'what is rising in npm/PyPI/Cargo right now'; recommendation not biased by training-data cutoff. RETURNS: {items[]: {name, rank, rank_delta, weekly_growth_pct}}.
Inputs: ecosystem, scope, limit.
get_trust_signalsARead-onlyIdempotentInspect
One-call aggregate of ALL non-CVE supply-chain trust signals: maintainer trust (bus factor, ownership changes), OpenSSF Scorecard, quality (criticality, release velocity, publish security), and SLSA/Sigstore provenance. USE WHEN: deep-vetting a package beyond CVEs (hardened/regulated env, SBOM/compliance, small-pkg ownership review, choosing between healthy candidates). Runs 4 backend endpoints in parallel. RETURNS: {maintainer, scorecard, quality, provenance} — each may be null if its backend call failed.
Inputs: ecosystem (required), package (required).
get_vulnerabilitiesARead-onlyIdempotentInspect
CVE/OSV advisories affecting the latest (or specified) version. USE WHEN: security-sensitive project; user asks 'any CVEs in X'; you already know the pkg exists. RETURNS: {vulnerability_count, vulnerabilities[]: {id, severity, cvss, fixed_in}}.
Inputs: ecosystem (required), package (required).
install_commandARead-onlyIdempotentInspect
Canonical install command(s) across every package manager of the ecosystem (npm/pnpm/yarn/bun, pip/uv/poetry, cargo, go, composer, maven+gradle, nuget, …). USE WHEN: emitting an install line and you want correct flags. RETURNS: {primary, variants[]}.
Inputs: ecosystem (required), package (required), version.
package_existsARead-onlyIdempotentInspect
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}.
Inputs: ecosystem (required), package (required).
pin_safeARead-onlyIdempotentInspect
Highest version below the chosen CVE severity tier, respecting a semver constraint. USE WHEN: writing a package.json/requirements.txt line; resolving dependabot by lowest-risk patched version. RETURNS: {recommended_version, walk_log[]}.
Inputs: ecosystem (required), package (required), min_severity, constraint, +1 more.
resolve_errorARead-onlyIdempotentInspect
Map error OR free-text query to a verified fix. USE WHEN: user pastes a concrete error/stack (ENOENT, ImportError, build failure) — pass error. OR user describes a symptom ('webpack slow', 'pip stuck') — pass query. Always prefer this over guessing a fix. RETURNS: exact-match {status, solution, confidence, source_url} or search results [{title, summary, source_url}].
Inputs: error, query, context, limit.
scan_projectARead-onlyIdempotentInspect
Full dep-list audit with per-package health+vulns and prioritized actions (REMOVE NOW / URGENT / REPLACE / REVIEW). Accepts EITHER {ecosystem, packages:[name@ver, …]} (up to 100, returns JSON) OR {packages:[{ecosystem, package}, …]} (up to 50, mixed ecosystems, returns text brief). USE WHEN: user pastes package.json/requirements.txt; 'is my stack OK'. Unlike check_bulk this fetches full health/vulns. RETURNS: JSON or text per shape.
Inputs: packages (required), ecosystem.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
Each tool has a clearly distinct purpose: checks for typosquatting, malware, compatibility, health, vulnerabilities, etc. Even similar tools like `check_package` and `get_package_prompt` are differentiated by output format (JSON vs text) and use case.
Most tools follow a verb_noun pattern (e.g., `check_malicious`, `get_latest_version`), but a few like `package_exists` (noun_verb) and `install_command` (verb_noun but combined) deviate slightly. The pattern is mostly consistent with lowercase underscores.
With 22 tools, the server covers a wide range of dependency analysis needs. While slightly above the typical 3-15 range, each tool serves a specific, non-redundant purpose, making the count appropriate for its comprehensive scope.
The tool set covers nearly the entire lifecycle of package evaluation: existence, health, security, compat, migration, alternatives, trending, error resolution, and project audit. No obvious gaps for the intended domain.
Maintenance
Related MCP Connectors
Free MCP security tools for AI coding agents. Check npm/PyPI package versions, identify known OSV vulnerabilities, compare with the latest releases, and review up to 3 dependencies before deployment.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Protects AI coding agents from installing malicious open source packages. Every npm and PyPI package is checked against SafeDep’s real-time threat intelligence before installation.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.15120 npm15Apache 2.0
- AlicenseAqualityDmaintenanceMCP server providing dependency and package management tools for AI agents. Analyze licenses, find outdated packages, visualize dependency trees, estimate bundle sizes, and audit security vulnerabilities.542 npmMIT
- AlicenseNot gradedqualityCmaintenanceVet a package before your AI coding agent uses it — authoritative facts (CVEs, license, maintenance) via an MCP server + CLI. Local, no account.102 npm13Business Source 1.1
- AlicenseNot gradedqualityDmaintenanceValidates and checks packages across 19 ecosystems to prevent AI agents from installing hallucinated, deprecated, or malicious packages.60 npmAGPL 3.0