Breaking Changes & Migration Data

Name: Breaking Changes & Migration Data
Author: nigelcox98

MCP serverMCP

What breaks when you upgrade a package, and what to use instead - from official docs.

by nigelcox98repository ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"breaking-changes-migration-data","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability110/110 checks ok

when	check	result	http	latency	detail
46 min ago	mcp initialize	ok	200	686 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
8 h ago	mcp initialize	ok	200	706 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
14 h ago	mcp initialize	ok	200	379 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
21 h ago	mcp initialize	ok	200	397 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
28 h ago	mcp initialize	ok	200	380 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
35 h ago	mcp initialize	ok	200	395 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	648 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	370 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	363 ms	server breaking-changes · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	397 ms	server breaking-changes · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

list_packages — List every package with breaking-change data available, including tracked versions and how many breaking changes each has. Call this first if you are unsure whe
get_breaking_changes — Get breaking changes for a package upgrade: removed APIs with their replacements and the reason for each, changed defaults, behavior changes, known incompatible
check_upgrade_safety — Given a package and the version you are upgrading TO, return a concise checklist an agent can act on: the count of breaking changes, the highest-risk removals,

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.nigelcox98/breaking-changes

first seen 1 mo ago · fetched 10 h agoopen ↗

Field history (6 recent events)

1 mo ago · declared · summary → "What breaks when you upgrade a package, and what to use instead - from official docs."
1 mo ago · declared · description → "What breaks when you upgrade a package, and what to use instead - from official docs."
1 mo ago · declared · publisherName → "nigelcox98"
1 mo ago · declared · repoUrl → "https://github.com/nigelcox98/AgentDataAPI"
1 mo ago · declared · version → "0.1.0"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from