Check whether your MCP server is ready for the next protocol release.
Upload a ZIP file or paste a public GitHub repository. You get a plain-English report on what breaks, what is deprecated, and what to ask your developer to change. No command line required.
Free plan includes 2 scans per month. No card required.
Point us at your code
Upload a ZIP up to 20 MB, or paste a public GitHub repository address. We scan a specific commit so the result is reproducible.
We read, never run
Your code is analysed statically. Nothing is executed, no dependencies are installed, and no package scripts run. Uploaded source is deleted as soon as the scan finishes.
Get an actionable report
A readiness score, what may stop working, and a checklist written for someone who does not know what MCP is — with the technical detail underneath for whoever does the work.
What we look for
The upcoming protocol revision removes the connection handshake, drops session identifiers, redesigns long-running work, changes error codes and requires new request headers. Each of those is a way a working server quietly stops working. We check for all of them and explain what each one means for your product.
Read this before you rely on it. A clean report means that no implemented rule fired. It does not guarantee complete compatibility with the target MCP specification.