dep-diff-mcp
Related Servers
Alternatives to dep-diff-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI coding agents to learn, from locally read lockfiles, what changes between the dependency version installed and a target version, which of the user's files that upgrade touches, and which vulnerabilities it resolves. It also performs OSV-matched vulnerability scans, ranks upgrade plans, and stores decision memory, running entirely on the user's machine with no account or API keys.11508 npmApache 2.0- AlicenseAqualityBmaintenanceEnables an AI agent to parse project lockfiles (npm, pnpm, Yarn, uv, Poetry, requirements.txt, Cargo, go.sum) and query OSV.dev to find known vulnerabilities in locked versions, transitive dependencies included, then produce minimal upgrade plans with breaking-change flags, cleanliness re-checks, and the parent dependency responsible. It also lists outdated packages and explains individual advisories, all read-only with no API key required.5MIT
- AlicenseAqualityBmaintenancePlans the change that closes your dependency alerts in uv and Poetry projects, verified with the project's own resolver on a temporary copy. Also sorts alerts that only reach dev tools and finds the exact Python floor that unblocks fixes.23,669 PyPI3MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.521 npmMIT
- AlicenseNot gradedqualityCmaintenanceAnalyzes npm dependency upgrades to reveal which files and functions in your codebase break, with confidence tiers and transitive call chain tracing.5 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides breaking changes analysis for libraries across multiple languages, enabling version upgrade planning, dependency audits, and migration reports through MCP tool access and expert workflows.-
TDQS
Scored across 2 tools
The two tools are clearly separated by scope: one handles a single package upgrade, the other handles multiple packages in bulk. Each description explicitly references the other, so an agent can unambiguously choose based on input size.
Both tools follow the same analyze_package_* pattern, with the singular 'change' and plural 'bulk' clearly differentiating them. This is a consistent and predictable verb_noun convention.
Two tools is minimal, but the server's narrow purpose of dependency upgrade analysis is well served by one individual and one bulk entry point. It is slightly thin but not unreasonable for the domain.
The pair covers both single-package and multi-package analysis, which covers most workflows. A minor gap is the lack of direct lockfile/diff parsing, but users can supply the package list from those sources.