Repository navigation
MCP-Warden 2.0.0 expands tool integrity commitments to cover annotations and output schemas. A change to either invalidates the reviewed tool surface rather than inheriting an old approval.
Migration
Fresh pins use schema level 4. Review existing locks, then re-pin and re-sign; older locks remain readable with their recorded coverage. SHA-256 commitments detect changes, and signatures establish provenance. Neither proves that a tool or its output is safe.
Packages
- Python:
pip install mcp-warden-cli==2.0.0 - TypeScript verifier 0.2.0:
npm install https://github.com/DataScience-EngineeringExperts/mcp-warden/releases/download/v2.0.0/mcp-warden-lock-0.2.0.tgz
The TypeScript package is distributed as an npm-installable GitHub asset. Wheel, source distribution, TypeScript tarball and SHA256SUMS have Sigstore verification bundles attached by the release workflow.
Validation and scope
The integrity feature passed 1218 Python tests, deterministic fuzz checks, MCP SDK 1.x/2.x capture checks, and cross-language conformance. The packaged TypeScript verifier passed 123 consumer tests. Release packaging preserves the existing PyPI trusted publisher and signing identity.
Migration and lock format · Changelog · Future Warden design
The protocol-neutral human checkpoint and broader prompt, retrieval, code and execution adapters are a documented proposal for future work.
Publication receipt
Published at merge 350d5ccc3cfd2bf079a8b7dadff5cdc6656fe51d. All package and checksum Sigstore bundles verify against this repository's release.yml@refs/tags/v2.0.0 identity and GitHub OIDC issuer. PyPI wheel and source distribution SHA-256 hashes match the signed GitHub assets exactly. Main-branch CI passed 1224 Python tests (2 skipped), 47 deterministic fuzz tests and SDK 1.x compatibility checks. Fresh PyPI install checks and the 123-test consumer check of the public TypeScript tarball pass. Public docs passed desktop and mobile visual checks.
The workflow's PyPI OIDC exchange rejected the existing trusted publisher configuration (invalid-publisher). This release was uploaded with the existing authorized PyPI token; automated trusted publishing still needs repair. Build, signing and docs deployment succeeded.