callstead

MCP release checks

Know what a tool
update changes.

Check saved calls against a new tool inventory. See exact failures before updating your integration.

Check a release

JSON files stay in this browser. No sign-in or server connection.

Example data. This fictional inventory contains a breaking update.

Up to 512 KiB per file, 100 tools and 200 cases. See the format

Your release report will appear here.

Load the example, or use two complete tools/list inventories and your recorded cases.

A schema change is only part of the story.

A new output can satisfy its own schema and still break a consumer written for the previous version. Callstead checks the supplied output against both contracts and the expectations you record.

Saved-call compatibility

Find the exact recorded inputs and outputs that no longer satisfy a contract.

Advertised behavior changes

Review changes to read-only, destructive, retry and external-access hints.

Evidence you can keep

Export a portable report and keep the exact findings with your release review.