All servers · Code & repositories
io.github.DigiCatalyst-Systems/dep-diff-mcp
io.github.DigiCatalyst-Systems/dep-diff-mcp · v0.3.2
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | prompts, tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.
Connect
streamable-http · https://dep-diff.digicatalyst.ca/mcp
claude mcp add --transport http dep-diff-mcp https://dep-diff.digicatalyst.ca/mcp{
"mcpServers": {
"dep-diff-mcp": {
"url": "https://dep-diff.digicatalyst.ca/mcp"
}
}
}Tools as reported by the server
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 advisories fixed in the range, migration guide links, and a clear recommendation. Use when the user asks about a specific panalyze_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). Use when the user provides many dependency changes from a Dependabot PR, npm outdated output, lockfile diff, or batch upg
Repository · JSON · Text for agents · Registry updated 2026-09-05