Read-only audit of AI Agent SDK and MCP server dependencies for breaking version jumps, schema drift and archived packages.
What you can do
Audit a manifest: check package.json, requirements.txt, pyproject.toml or .mcp.json contents for breaking major version jumps, unpinned @latest servers and archived packages, with exact pin commands
Inspect one package: look up live npm or PyPI version, publish date, 90-day release velocity, stability score and tools/list schema drift risk, plus before/after migration code
Rank volatility: list the fastest-changing or highest drift-risk SDKs and MCP servers, filtered by kind, category or result limit
Find replacements: get the migration matrix for archived @modelcontextprotocol/server-* reference packages and their vendor-maintained successors
When to use it
Useful when maintaining an agent or MCP configuration and you want to know whether pinned dependencies are outdated, likely to break, or built on archived reference servers before upgrading or shipping.
Requirements
Remote Streamable HTTP endpoint, or a local run via npx over stdio. No authentication, API keys or environment variables are declared.
Before you install
All four tools are described as read-only lookups, but check_stack_drift takes the raw contents of your manifest files, which may reveal internal package names and versions to the hosted service. No credentials are requested.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.joeyg6393%2Fagentbreakwatch-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Official Model Context Protocol (MCP) server for AgentBreakWatch, the live breaking-change and tools/list JSON Schema drift telemetry index across 32 core AI Agent SDKs and 226 MCP servers (258+ total tracked packages) on npm and PyPI.
check_stack_drift: Pass the raw contents of a .mcp.json, package.json, requirements.txt, or pyproject.toml file to detect breaking major version jumps, unpinned @latest MCP servers, and archived packages, with exact version pin commands across 258+ tracked packages.
get_package_stability: Retrieve live npm/PyPI version, publish date, 90-day release velocity, 0-100 stability score, tools/list schema drift risk, and copy-paste before/after migration code for any of the 258+ tracked packages.
list_volatile_packages: Query the fastest-changing Agent SDKs and MCP servers over the last 90 days, optionally filtered by kind (sdk or mcp) or ecosystem category.
get_archived_mcp_replacements: Retrieve the migration matrix for archived @modelcontextprotocol/server-* packages (server-github, server-postgres, server-puppeteer, server-brave-search, server-redis) and their official 2026 vendor-maintained replacements.
Read-only audit of a package.json, requirements.txt, or .mcp.json configuration string against 256 live AI Agent SDKs and MCP servers. Flags breaking major version deltas, unpinned @latest MCP servers, and outdated dependencies with exact pin commands. Requires no authentication and returns a structured JSON report.
Parametersmanifestrequired
get_package_stability
Get Single Package Stability and Migration Diff
Read-only lookup of live npm or PyPI version, publish timestamp, 90-day release velocity, stability score (0-100), MCP tools/list schema drift risk, and before/after migration code for a single AI Agent SDK or MCP server. Prefer this over check_stack_drift when inspecting one specific package by name or slug.
Parameterspackagerequired
list_volatile_packages
List Most Volatile AI Agent SDKs and MCP Servers
Read-only query that lists the fastest-changing or highest schema-drift-risk AI Agent SDKs and MCP servers from the live AgentBreakWatch telemetry index, sorted descending by 90-day release velocity. Supports filtering by kind ('sdk', 'mcp', 'all'), category hub slug, and result limit (1-50).
Parameterskindlimitcategory
get_archived_mcp_replacements
Get Archived Reference MCP Replacement Matrix
Read-only lookup returning the complete migration matrix for archived or frozen @modelcontextprotocol/server-* reference packages and their official 2026 vendor-maintained replacements. Takes no parameters and requires no authentication.
Takes no parameters.
Version history
2
v1.2.0LatestOct 26, 2026
v1.1.0Oct 25, 2026
Score
100%
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.