io.github.DigiCatalyst-Systems/dep-diff-mcp
NPM · @DIGICATALYST/DEP-DIFF-MCP · 2 COMPONENTS
Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.
Available components
Last scanned (21 hours ago)
Scores higher than 99% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to DigiCatalyst-Systems/dep-diff-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 346 tokens (~173/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.2 → 0.3.3 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@digicatalyst/dep-diff-mcp@0.3.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | DigiCatalyst-Systems/dep-diff-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/DigiCatalyst-Systems/dep-diff-mcp/.github/workflows/publish.yml@refs/tags/v0.3.3 |
| Rekor log index | 3579713761 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3ae7b42db61b6e08c61fab91ff152024728b328608ff4b718638d53e2a31affc0c26c70802018e3e2a875bf772fe1acb26ab748d39386c3815875e975 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_package_change Analyze a single dependency version change ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem |
| fromVersion | string | yes | Current version (e.g. '18.2.0') |
| name | string | yes | Package name (e.g. 'react', 'requests') |
| toVersion | string | yes | Target version (e.g. '19.0.0') |
| Name | Type | Req | Description |
|---|---|---|---|
| breakingChanges | array | yes | Breaking changes extracted from release notes; empty when none were found |
| ecosystem | string | yes | Package ecosystem |
| fromVersion | string | yes | Version being upgraded from |
| migrationLinks | array | yes | Migration or upgrade guide URLs found in release notes |
| package | string | yes | Package name that was analyzed |
| recommendation | string | yes | Single-line verdict explaining the recommendation level |
| recommendationLevel | string | yes | Risk classification, used to rank packages in bulk results |
| releaseCount | number | yes | Number of GitHub releases found strictly between the two versions |
| releaseExcerpts | array | – | Raw release-note excerpts, present only as a fallback when a major/minor bump yielded no breaking changes |
| repoUrl | string|null | yes | Source repository URL, or null when none could be resolved |
| securityFixes | array | yes | Advisories affecting fromVersion that are resolved at toVersion |
| semverClass | string | yes | Semver relationship between the two versions |
| toVersion | string | yes | Version being upgraded to |
No examples provided.
analyze_packages_bulk Analyze multiple dependency changes in parallel ~119
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).
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | List of package changes to analyze |
| Name | Type | Req | Description |
|---|---|---|---|
| bySemverClass | object | yes | Breakdown of the batch by semver class |
| packages | array | yes | Per-package results, ranked security > caution > review > likely-safe > safe |
| packagesWithBreakingChanges | number | yes | How many packages had at least one breaking change |
| securityFixesTotal | number | yes | Total security advisories resolved across the whole batch |
| totalPackages | number | yes | Number of package changes submitted |
No examples provided.
How do I install the io.github.DigiCatalyst-Systems/dep-diff-mcp server?
io.github.DigiCatalyst-Systems/dep-diff-mcp runs locally as an npm package, launched with npx -y @digicatalyst/dep-diff-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @digicatalyst/dep-diff-mcp
claude mcp add digicatalyst-systems-dep-diff-mcp -- npx -y @digicatalyst/dep-diff-mcp
What is the io.github.DigiCatalyst-Systems/dep-diff-mcp server?
io.github.DigiCatalyst-Systems/dep-diff-mcp is listed in the public MCP registry as io.github.DigiCatalyst-Systems/dep-diff-mcp. Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions. This page covers its npm package (@digicatalyst/dep-diff-mcp).
Is the io.github.DigiCatalyst-Systems/dep-diff-mcp server safe to use?
io.github.DigiCatalyst-Systems/dep-diff-mcp scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.DigiCatalyst-Systems/dep-diff-mcp server expose?
io.github.DigiCatalyst-Systems/dep-diff-mcp exposes 2 tools: analyze_package_change, analyze_packages_bulk. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.
Is the io.github.DigiCatalyst-Systems/dep-diff-mcp server still maintained?
io.github.DigiCatalyst-Systems/dep-diff-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.DigiCatalyst-Systems/dep-diff-mcp server under?
io.github.DigiCatalyst-Systems/dep-diff-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.