Frequently asked questions
Do you run my code?
No. The scanner reads your source files as text and parses them. Nothing is executed, no module is imported, no package scripts run, no dependencies are installed, and the scan itself has no network access.
What happens to the code I upload?
The uploaded archive is stored only until the worker picks it up, then deleted. The unpacked source is removed as soon as the scan finishes — including when it fails or times out. We keep the report; we do not keep your code.
Can you scan a private repository?
Not in this release. Only public GitHub repositories are supported. For a private project, upload a ZIP instead.
Does a clean report mean I am safe to upgrade?
No, and we will not claim otherwise. A clean report means that no implemented rule fired. It does not guarantee complete compatibility with the target MCP specification.
What is the readiness score?
A heuristic this tool produces by deducting points for each finding, weighted by severity and confidence. It is a way to compare one scan to another. It is not an official certification, score or endorsement of any kind.
Why does the report say the target is a release candidate?
Because it is. The rules target a revision whose final specification is not yet published. We would rather say so on every report than let you discover it later.
Is there a free command-line version?
Yes, and it is the same scanner. It is MIT-licensed and available at github.com/JacobRyan258/mcp-upgrade. The hosted service exists for people who would rather not use a terminal.
What counts against my monthly allowance?
One scan is reserved when you submit. If the scan completes, it is counted — whether or not it found anything. If it fails for any reason, including a problem with your upload or a fault on our side, the reservation is released and you are not charged for it.
How do I cancel?
From the billing portal, linked in your dashboard. Cancelling keeps Pro until the end of the period you have already paid for, then drops you to Free.