The everyday value is that an agent tomorrow, in a different tool, can read what was already checked instead of re-deriving it, and the stamp goes STALE the moment someone edits the file without re-verifying. The stronger version is replay: attach a command to the claim and it comes back CONFIRMED, CONFIRMED_DRIFTED, REFUTED, or UNREPLAYABLE when no recipe exists.
A trust-metadata format and MCP server. Files carry a stamp recording who produced them, what was verified and when — readable by the next agent in any tool, across sessions.
- 11 tools: check_file, replay_file, create_claim, validate_file, scan_file, trust_score, stamp_file, audit_file, embed_file, extract_file, detect_threats
- A trust score from 0 to 1, weighted by evidence and source tier
- Verification evidence with timestamps — tests passed, type check clean, human reviewed
- STALE detection when a file is modified after its stamp, with a non-zero exit code you can gate CI on
- Replay: a stamp can carry a runnable probe, re-executed rather than trusted
- Compliance reporting, including an EU AI Act mapping
Pip install akf, or npm install akf-format for TypeScript, then akf init --git-hooks. The MCP server installs separately from packages/mcp-server-akf and runs as python -m mcp_server_akf. Version 1.6.0.
One command — pip install ./packages/mcp-server-akf