PASS secure evidence
One local command accepts a synthetic packet with HTTPS discovery, CIMD identity matching, S256, exact localhost callback, and bound resources.
Lock the publisher, source, protocol, capability surface, and OAuth boundary of a third-party MCP dependency. Catch drift, hostile metadata, and unsafe authorization evidence in CI. Keep the proof in your repo.
The Maintainer Edition includes a redacted evidence gate for the remote-auth seams that are hardest to review by inspection: issuer binding, PKCE S256, exact redirects, resource indicators, and token audience/passthrough handling.
One local command accepts a synthetic packet with HTTPS discovery, CIMD identity matching, S256, exact localhost callback, and bound resources.
The companion packet fails closed on wrong issuer, missing discovery, plain PKCE, wildcard redirect, missing resource indicators, and token-validation gaps.
No OAuth flow, token, model, or network call is hidden in the proof. The pack is honest evidence scaffolding for a real integration test.
Record endpoint, publisher, source repository, immutable revision or artifact digest, negotiated protocol, and contract digest.
Block removed tools, removed properties, new required fields, narrowed enums, protocol changes, metadata rewrites, and side-effect escalation.
Generate Markdown, JSON, SARIF, and JUnit from the same deterministic run. Keep contract and OAuth review artifacts with the pull request.
No. Core admission, drift, lint, and fixtures are offline and dependency-free. It does not send tool metadata, secrets, or prompts anywhere.
No. It is evidence for the recorded surface and chosen fixtures. It does not prove runtime authorization, safe outputs, absence of vulnerabilities, or regulatory compliance.
Use Inspector for interactive debugging. ChangeGuard adds a committed provenance lock, semantic drift classification, deterministic negative fixtures, and CI artifacts for an admission decision.
No. It checks a redacted, captured evidence packet without fetching metadata, handling credentials, or inspecting tokens. That makes the result safe to run in CI; pair it with your own authenticated integration test for live behavior.