Paste Your Agent Stack to Detect Breaking Releases & Drift
Compare your `.mcp.json`, `package.json`, or `requirements.txt` against our live index of 30 Agent SDKs and 226 MCP servers. We flag major version jumps, archived official MCP servers, and unpinned `@latest` servers that can silently break tool calls.
Major or breaking version delta (1.0.2 -> 2.0.0). Major v2.0.0 release enforces roots protocol capabilities, tightens symlink path traversal validation, and updates edit_file dryRun diff schema.
npx -y @modelcontextprotocol/server-filesystem@2.0.0Matches live NPM version v2025.4.8 (published 2025-04-08).
npx -y @modelcontextprotocol/server-github@2025.4.8Major or breaking version delta (0.9.0 -> 0.14.0). v0.14.x supports --read-only and --project-ref scoping; execute_sql and apply_migration split DDL vs DML operations.
npx -y @supabase/mcp-server-supabase@0.14.0Unpinned (@latest) dependency with HIGH schema drift risk. Silent tool schema or export shifts will hit production immediately. Pin to v0.0.83.
npx -y @playwright/mcp@0.0.83Major or breaking version delta (2.1.0 -> 3.34.1). v3.x upgrades to Firecrawl v2 API: firecrawl_extract requires schema or prompt, and firecrawl_scrape removes deprecated pageOptions.
npx -y firecrawl-mcp@3.34.1Running `npx -y @org/mcp-server@latest` in production pulls new `tools/list` input schemas on every container restart. Always pin exact versions.
Several early `@modelcontextprotocol/server-*` packages (`server-github`, `server-postgres`, `server-puppeteer`) are archived and superseded by vendor-maintained servers.
Save your stack once to get instant email or Slack/webhook alerts with tested before-and-after code snippets whenever a dependency ships a breaking change.
Get Instant Breaking-Change Alerts
Receive an email with before/after fix snippets the moment a tracked SDK or MCP server ships a breaking release.