Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsMCP Migration Compatibility Checker (2025→2026)
Compare fixed MCP contract snapshots for revisions 2025-11-25 and 2026-07-28 and get local PASS, FAIL or NEED_USER evidence.
Free
MCP Migration Compatibility Checker (2025→2026)
Example session with this skill installed
Verify the migration compatibility between ./snapshots/old_contract.json and ./snapshots/new_contract.json. Output the results to the ./audit-logs directory.
- Read your context and instructions
- Compiled the mcp migration compatibility
Audit complete. Status: FAIL. Found 2 BREAKING changes in tool schema required fields.
Artifacts generated
- compatibility.json (authoritative)
- compatibility.md (summary)
- evidence-receipt.json
Connects securely to your tools. The creator never sees your data.
About this skill
A contract migration can appear compatible until a renamed or unsupported field reaches release review. Compare one local 2025-11-25 baseline snapshot with one 2026-07-28 candidate snapshot and receive a deterministic compatibility decision plus five reviewable evidence files. This checker supports only that fixed revision boundary and does not connect to a live MCP server.
The problem
Manually verifying Model Context Protocol (MCP) contract compatibility during the 2025-to-2026 era migration is error-prone. Developers lack a deterministic way to audit breaking changes between local protocol snapshots without risking subjective LLM hallucinations.
What it does
- Performs deterministic comparison between 2025-11-25 and 2026-07-28 MCP snapshots.
- Generates five auditable artifacts including compatibility reports and evidence receipts.
- Enforces a fail-closed gate resulting in PASS, FAIL, or NEED_USER based on migration rules.
- Validates JSON depth, value-node counts, and type-aware canonical semantics.
- Detects breaking changes in tools, prompts, and schema annotations via local execution.
Frameworks & tools
Python, Model Context Protocol (MCP), JSON Schema, SHA-256 integrity hashing.
Why this beats prompting it yourself
Prompting an LLM to "check for compatibility" leads to missed edge cases in JSON schema evolution. This tool uses a rigid, script-based collector that prevents subjective upgrades of FAIL or NEED_USER statuses, ensuring 100% auditability.
Use cases
- Verifying tool and prompt compatibility before upgrading MCP server implementations.
- Generating compliance evidence for internal architectural reviews.
- Debugging malformed JSON schema transitions between protocol revisions.
Known limitations
Only supports the 2025-11-25 to 2026-07-28 revision boundary. Rejects network shares, remote volumes, and Windows UNC paths. Does not perform automatic fixes or tool execution.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
1 install
Downloaded by developers to date
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 1 month ago
- Free to download with an account