Manifest change classified
The tool manifest changed since the pinned run and this check sorts the change into breaking, additive or semantic drift.
What it means
MANIFEST-001 fires one line when anything in the tool manifest changes. This check is the breakdown. It sorts every change into one of three buckets so a reviewer can tell at a glance whether client code needs to change. Breaking (critical): a tool was removed, a parameter was removed, a parameter was made required, a parameter's type was narrowed or an enum lost a value. Existing clients will fail. Semantic drift (medium): the shape is identical but a tool description changed. The schema that a client codes against has not moved, but the text the model reads to plan has. The tool can start behaving differently without any code change on the client side. Additive (low): a new tool or a new optional parameter appeared. Existing clients keep working. MANIFEST-001 and MANIFEST-002 fire on the same change. 001 is the single alert, 002 is the detail. The check stays silent when no earlier run was pinned.
How to fix
For breaking changes treat the server like a major version bump: notify clients or hold until they upgrade. For semantic drift read the description diff and confirm it still matches what the tool actually does. For additive changes no action is needed. In all cases re-pin the manifest with `--trust` once the change has been reviewed.
Run the check against your own server:
npx -y @patchbay-nebius/agent audit <url-or-directory>No install: scan an MCP server in the browser and get a shareable report.
Disagree with this finding on your server? Open an issue with the --json output. False-positive reports are the most useful feedback.