// SCAN REPORT

Depscope

22 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 13 Aug 2026

2 can modify or destroy data

20 read-only

22 tools total

Community server · catalogue entry checked 13/08/2026 · full schemas captured for 22 of 22 tools

How to control Depscope ↓

TOOL MAP

What Depscope exposes to your agents

Read (20) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Depscope costs in tokens

4,348 tokens of tool definitions, loaded on every request

2.2% of a 200k context window

477 heaviest tool: contact_depscope

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Depscope tools

Write · Low pin_safe The tool reads package metadata to recommend safe versions, but its stated USE WHEN indicates it's meant to update package dependency files—a write operation. Write · Low contact_depscope This tool creates a support/reporting ticket (bug, listing, security disclosure, anomaly, or partnership request) and returns a ticket or anomaly ID.

2 of Depscope's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Depscope

PolicyLayer is an MCP gateway — it sits between your AI agents and Depscope, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "contact_depscope": {
    "limits": [
      {
        "counter": "contact_depscope_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_bulk": {
    "limits": [
      {
        "counter": "check_bulk_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Depscope — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DEPSCOPE →

Instant setup, no code required.

FULL CATALOGUE

All 22 Depscope tools

WRITE 2 tools

Write contact_depscope Inbound ticket: bug/listing/security/anomaly/partnership. USE WHEN: reporting wrong data (bug), requesting a n Write pin_safe Highest version below the chosen CVE severity tier, respecting a semver constraint. USE WHEN: writing a packag

READ 20 tools

Read check_bulk Fast pre-flight filter for a batch of (ecosystem, package) pairs. DB-only, <100ms for 100 items. USE WHEN: abo Read check_compatibility Is this specific multi-package version combo verified to work together? USE WHEN: pinning a stack (next@15 + r Read check_malicious Supply-chain malware check against OpenSSF/OSV. USE WHEN: about to suggest install of an unvetted/unfamiliar p Read check_package Full machine-readable JSON report (~2k tokens). USE WHEN: you need to programmatically parse specific fields ( Read check_typosquat Typosquat detector. USE WHEN: name differs from a well-known package by 1-2 chars (lodsh, reqeusts); copy-past Read compare_packages Side-by-side comparison (health, vulns, downloads, maintainers, last release) of 2-10 packages in the same eco Read find_alternatives Curated replacements for deprecated/unhealthy packages, including stdlib built-ins (e.g. fs.rm for rimraf). US Read get_breaking_changes Breaking changes between two majors of the SAME package (next@14→15). USE WHEN: user is bumping a major; befor Read get_health_score Single 0-100 health score — cheapest go/no-go gate (>=70 safe). USE WHEN: CI gating or pkg already screened fo Read get_known_bugs Non-CVE known bugs for a specific package version. USE WHEN: unexpected behavior that is NOT a security issue; Read get_latest_version Latest published version + deprecation flag — the cheapest call. USE WHEN: only a version string matters (pinn Read get_migration_path Prescriptive migration plan between DIFFERENT packages — rationale + literal code diff + breaking changes + ef Read get_package_prompt LLM-optimised package brief — plain text ~300 tokens (~75% cheaper than JSON). Verdict (SAFE/AVOID/URGENT/MALI Read get_trending Live trending packages with rank-delta and weekly growth %. USE WHEN: 'what is rising in npm/PyPI/Cargo right Read get_trust_signals One-call aggregate of ALL non-CVE supply-chain trust signals: maintainer trust (bus factor, ownership changes) Read get_vulnerabilities CVE/OSV advisories affecting the latest (or specified) version. USE WHEN: security-sensitive project; user ask Read install_command Canonical install command(s) across every package manager of the ecosystem (npm/pnpm/yarn/bun, pip/uv/poetry, Read package_exists Boolean registry existence check. USE WHEN: about to emit a package name in an install command but unsure it e Read resolve_error Map error OR free-text query to a verified fix. USE WHEN: user pastes a concrete error/stack (ENOENT, ImportEr Read scan_project Audit a project's dependencies in one shot. Returns a single-sentence verdict (e.g. "DO NOT INSTALL — 1 halluc

FAQ

Questions about Depscope

How do I prevent bulk modifications through Depscope? +

The Depscope server has 2 write tools including contact_depscope, pin_safe. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Depscope.

How many tools does the Depscope MCP server expose? +

22 tools across 2 categories: Read, Write. 20 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Depscope? +

Register the Depscope MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Depscope tool call.

Deterministic rules across all 22 Depscope tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DEPSCOPE →

Instant setup, no code required.

22 Depscope tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Depscope's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →