How it works

1. Screen. Before you approve a tool, every string in its definition (description, titles, schema descriptions, enum values) is screened for hidden instructions and invisible characters.
2. Pin. On approval, the definition is hashed (canonical JSON, keys sorted, equal numbers treated equal) and stored for your key, that server and that tool name. A flagged definition is pinned only when a person acknowledges the findings.
3. Verify. Before each use, send what the server presents now. A different hash is drift, with a field-level diff to the exact nested field.
4. History. Every pin, re-pin (with the previous hash) and verification is kept.

FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.