explain_package_upgrade

2 registry entries were observed exposing a tool named explain_package_upgrade — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,474 of 40,852 scannable entries (31%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @digicatalyst/dep-diff-mcpMCPattestedlivetrust 85/100 · A

   v0.3.2

   ↓ 87/wk

   ★ 1

   MCP server that translates a lockfile diff into a human-readable upgrade plan.

   ClaudeCursorCopilotChatGPTGemini

   Kaustubh GhodkeMIT1mo agonpmGitHub+compareobserved 2026-08-30 · static extraction

   mcpmodel-context-protocoldependencieschangelogcvedependabot
2. io.github.DigiCatalyst-Systems/dep-diff-mcpMCPattestedtrust 85/100 · A

   v0.1.10

   ★ 2

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

   ClaudeCursorCopilotGemini

   io.github.DigiCatalyst-SystemsUnknown5mo agonpmGitHub+compareobserved 2026-06-13 · static extraction

   mcp

All indexed toolsSearch the registry for explain_package_upgrade