Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.
Scored across 2 tools
The two tools split cleanly by cardinality: one analyzes a single package upgrade, and the other handles batches of upgrades. Their descriptions even cross-reference each other to route the agent correctly, so there is no overlap or ambiguity.
Both tools share an 'analyze_package(s)_...' verb-noun prefix and lowercase snake_case convention. The slight asymmetry between 'package_change' (singular) and 'packages_bulk' (plural + suffix) is minor but predictable.
With only two tools, the server is on the thin side of the typical 3-15 tool range. Both tools are substantial and cover a focused workflow, which makes the count understandable, but it still feels minimal for a dependency-diff server.
The single/bulk split covers the core upgrade-analysis workflow without dead ends, since the bulk tool handles many packages and the single tool provides depth. Minor gaps exist around lockfile or dependency-tree diffing, but agents can work around them by feeding package lists to the bulk tool.
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.
Inputs: name (required), ecosystem (required), toVersion (required), fromVersion (required). Returns: package, repoUrl, ecosystem, toVersion, +9 more
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).
Inputs: changes (required). Returns: packages, bySemverClass, totalPackages, securityFixesTotal, +1 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Deterministic package.json upgrade plans: age gate, aligned peers, reasons per change. No AI.
Diff two npm/PyPI versions or lockfiles: new install scripts, network/shell/eval calls, new deps.
Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.
Check exact npm/PyPI upgrades for evidence-backed breaking changes; query APIs and components.
Add one secure layer between your agents and this server.