Skip to content

io.github.DigiCatalyst-Systems/dep-diff-mcp

by DigiCatalyst-Systems · remote · local (npm) · no sign-in to list tools · v0.3.2 · published by GitHub user DigiCatalyst-Systems

Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.

Read only
CompareRegistry entry

2 tools: 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http dep-diff https://dep-diff.digicatalyst.ca/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Only reads 2Claude Code: allow
  • analyze_package_changeGiven one package and two versions (from -> to), returns a structured upgrade analysis: semver classification, GitHub release notes summary, detected breaking changes, security adv…No findings

    Why it is in this group

    • The name "analyze_package_change" says "analyze": a word for reading.
    Description, as the server wrote it
    Given one package and two versions (from -> to), returns a structured upgrade analysis: semver classification, GitHub release notes summary, detected breaking changes, security advisories fixed in the range, migration guide links, and a clear recommendation. Use when the user asks about a specific package upgrade ('what changed between react 18 and 19', 'is it safe to bump axios from 0.27 to 1.0', 'what does upgrading lodash 4.17.20 to 4.17.21 fix'). Supports npm, pypi, and github-actions (use the action reference as the name, e.g. actions/checkout). For analyzing many packages at once or a Dependabot batch, use analyze_packages_bulk instead.

    Annotations the server declares

    • title: Analyze a single dependency version change
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • analyze_packages_bulkAnalyzes a list of package upgrades in parallel and returns a unified risk report with packages ranked by recommendation level (security > caution > review > likely-safe > safe).No findings

    Why it is in this group

    • The name "analyze_packages_bulk" says "analyze": a word for reading.
    Description, as the server wrote it
    Analyzes a list of package upgrades in parallel and returns a unified risk report with packages ranked by recommendation level (security > caution > review > likely-safe > safe). Use when the user provides many dependency changes from a Dependabot PR, npm outdated output, lockfile diff, or batch upgrade. Returns: total count, breakdown by semver class, total security fixes found, packages with breaking changes, and per-package details. Limit 50 packages per call (chunk larger lists).

    Annotations the server declares

    • title: Analyze multiple dependency changes in parallel
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.3.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http dep-diff https://dep-diff.digicatalyst.ca/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dep-diff__analyze_package_change",
      "mcp__dep-diff__analyze_packages_bulk"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as dep-diff. Review it before you use it.