Integrity Simulated 3 MCP tools

Integrity Engine

Checksum visualization and tamper detection.

How you use it

Run integrity_enforce on release artifacts and sensitive configs. Investigate mismatches — do not regenerate expected hashes to “make it pass.”

Token savings

Stops silent corruption and “why does prod disagree?” hunts after bad publishes.

Consistency

Tamper detection is mandatory on declared integrity targets.

In action

Integrity

Hash

Checksums for artifacts / critical files.

Compare

Tamper

Hold

Interactive demo

SHA-256

e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

✓ Integrity verified

Simulated behavior only — does not execute proprietary AGS engine code.

Diagram

Example usage

# MCP: integrity_enforce
{}

# Expected
sha256: <digest>  path: dist/index.js