# DepScope (remote · mcp.depscope.dev)

Package intelligence MCP for AI agents — 22 tools, 19 ecosystems, AGPL SDK, free.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.depscope.dev`: 64/100 (this document), [markdown](https://verifymcp.io/servers/dev-depscope-mcp/mcp.md), [page](https://verifymcp.io/servers/dev-depscope-mcp/mcp)
- npm · `depscope-mcp`: 67/100, [markdown](https://verifymcp.io/servers/dev-depscope-mcp/depscope-mcp.md), [page](https://verifymcp.io/servers/dev-depscope-mcp/depscope-mcp)

## Channel facts

- Endpoint: `https://mcp.depscope.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.9.24`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3060 tokens (~139/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 48% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-depscope-mcp https://mcp.depscope.dev/mcp
```

### Codex

```toml
[mcp_servers.dev-depscope-mcp]
url = "https://mcp.depscope.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-depscope-mcp": {
      "type": "remote",
      "url": "https://mcp.depscope.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-depscope-mcp --url https://mcp.depscope.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-depscope-mcp:
    url: "https://mcp.depscope.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-depscope-mcp": {
      "type": "http",
      "url": "https://mcp.depscope.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (22)

### `check_malicious` (~83 tokens)

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}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `check_typosquat` (~84 tokens)

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}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `check_bulk` (~125 tokens)

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}.

Input parameters:

- `items` (array, required)

### `package_exists` (~58 tokens)

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}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `get_latest_version` (~78 tokens)

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}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `get_health_score` (~89 tokens)

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}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `install_command` (~103 tokens)

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[]}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)
- `version` (string): Optional explicit version; defaults to latest.

### `get_package_prompt` (~113 tokens)

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.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `check_package` (~109 tokens)

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}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required): Package name (e.g. 'express', 'fastapi', 'serde').
- `version` (string): Specific version (optional; default = latest).

### `get_vulnerabilities` (~85 tokens)

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}}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `find_alternatives` (~92 tokens)

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}}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `get_migration_path` (~113 tokens)

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}.

Input parameters:

- `ecosystem` (string, required)
- `from_package` (string, required): Deprecated/legacy package to migrate away from.
- `to_package` (string, required): Modern replacement package.

### `get_breaking_changes` (~103 tokens)

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}}.

Input parameters:

- `ecosystem` (string, required)
- `from_version` (string)
- `package` (string, required)
- `to_version` (string)

### `pin_safe` (~133 tokens)

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[]}.

Input parameters:

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

### `scan_project` (~244 tokens)

Audit a project's dependencies in one shot. Returns a single-sentence `verdict` (e.g. "DO NOT INSTALL — 1 hallucinated: fastapi-turbo") that an agent can paste into its reply, plus per-package health/vulns/recommendation. Detects hallucinated packages, deprecated, typosquats, critical vulnerabilities. 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/Cargo.toml; agent generated install command; 'is my stack OK'. RETURNS: JSON with `verdict`, `project_risk`, `summary.hallucinated_packages`, `summary.deprecated_packages`, per-package health.

Input parameters:

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

### `compare_packages` (~96 tokens)

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.

Input parameters:

- `ecosystem` (string, required)
- `packages` (array, required): Package names to compare, e.g. ['express','fastify','hono'].

### `check_compatibility` (~81 tokens)

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}.

Input parameters:

- `packages` (object, required): Package -> version map, e.g. {"next":"15","react":"19"}.

### `resolve_error` (~166 tokens)

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}].

Input parameters:

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

### `get_known_bugs` (~76 tokens)

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}}.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)
- `version` (string)

### `get_trust_signals` (~140 tokens)

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.

Input parameters:

- `ecosystem` (string, required)
- `package` (string, required)

### `get_trending` (~112 tokens)

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}}.

Input parameters:

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

### `contact_depscope` (~403 tokens)

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}.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-depscope-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://mcp.depscope.dev/mcp
- Repository: https://github.com/cuttalo/depscope-mcp
- Website: https://depscope.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-depscope-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-depscope-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-depscope-mcp/mcp