check_fileLABSCO SUMMARY
A stamp is cached verification state — and it can carry a probe that re-runs.
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.
What it is
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.
What you get
- 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
Requirements
pip install akf, or npm install akf-format for TypeScript, then akf init --git-hooks. The MCP server is a separate PyPI package — pip install mcp-server-akf — and runs as python -m mcp_server_akf. Version 1.6.0.
Setup effort
One command — pip install mcp-server-akf
USE CASES
Not re-verifying what a previous session already checked
Check the file first; a fresh stamp with real evidence means you can build on it.
Marking work as verified when the tests pass
Stamp the file with the evidence, so the next reader knows what was actually run.
Re-running a claim instead of believing it
Execute the stored probe and see whether it still holds against the current world.
Producing a compliance report over a repository
Scan and audit against a named regulation rather than assembling it by hand.
11 tools
Listed in project docs. Your client may show a different list.
replay_filecreate_claimvalidate_filescan_filetrust_scorestamp_fileaudit_fileembed_fileextract_filedetect_threatsBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
python on PATH
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
pip install mcp-server-akfMCP Clients
Claude Code, Any MCP client
{
"mcpServers": {
"akf": {
"command": "python",
"args": [
"-m",
"mcp_server_akf"
]
}
}
}