Upgrade Brief

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as dev.workers.shopttyass-85f.upgrade-brief/upgrade-brief and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 22 Oct 2026. Not supplied by the maker.

• npm_breaking_changes

  npm breaking changes between two versions of a package, read from its real CHANGELOG and GitHub release notes: documented breaking items per version, major bumps, Node.js engine / ESM-CJS / peer depen

• npm_changelog

  npm changelog between two versions: full release notes of every version in the range (newest first), with dates, bump type, deprecations, extracted breaking changes and package.json changes. Paid: $0.

• pypi_breaking_changes

  PyPI breaking changes between two versions of a Python package, from its CHANGELOG/HISTORY/CHANGES file and GitHub releases: breaking items per version, Requires-Python and dependency changes, yanked

• pypi_changelog

  PyPI changelog between two versions of a Python package: full release notes per version (newest first) with dates, bump type, yanked flags, extracted breaking changes and Requires-Python / dependency

• dependency_upgrade_plan

  Dependency upgrade plan for up to 5 npm or PyPI packages: per package the breaking changes to the target version, major bumps, engine/Python and peer dependency changes, migration guides and a risk sc

• npm_versions

  Free: published versions of an npm package (newest first) with publish dates, bump type and deprecations, to pick valid from/to values.

• pypi_versions

  Free: published versions of a PyPI project (newest first, PEP 440 order) with publish dates and bump type.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.