Trust metadata for AI agents β check files before building on them, stamp verified work.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
A stamp costs ~15 tokens. Re-verifying costs 15,000.
Think EXIF for AI β trust metadata that travels with every AI-generated file,
so the next agent (or human) knows what it can build on.
β Star on GitHub Β· Website Β· π‘οΈ Is This AI-Generated? Β· πͺπΊ Compliance Check Β· π Repo Scanner
Quickstart Β· AI Agents Β· MCP Server Β· Agent Skills Β· CLI Β· Website
Don't install AKF yourself β let your agent do it. Paste this into Claude Code, Cursor, OpenClaw, or any coding agent:
Your agent installs its own provenance layer β and every file it touches carries trust metadata from then on.
Agents redo work constantly: re-read files, re-run tests, re-derive conclusions β because nothing tells them what was already verified. A stamp is cached verification state:
Stamps are trail markers agents leave for other agents β across sessions, across tools (Claude Code β Cursor β Copilot), across teams. Humans get the same trail: who made this file, AI or human, was it tested, can we trust it.
| What travels with the file | How |
|---|---|
| Trust score | 0β1 confidence, weighted by evidence and source tier |
| Verification evidence | tests passed, type check clean, human reviewed β with timestamps |
| Source provenance | SEC filing β analyst β AI agent chain |
| Compliance | One command: akf audit file --regulation eu_ai_act |
A signature proves who said it; a replay proves it could have been true. A stamp can carry a falsifiable probe recipe, so the next agent re-verifies the claim instead of trusting the label:
REFUTED when the probe fails, UNREPLAYABLE when there's no recipe. This is the answer to "a trusted source can still be wrong": trust stops depending on who signed it, for any claim with a runnable check.
akfcommand not found? Runakf doctorto auto-detect your setup, or usepython3 -m akf(always works).
- Install with pipx:
pipx install akf(recommended β auto-handles PATH)- Windows: use
python3 -m akfor install viapipx
TypeScript / Node.js (akf-format):
Full TypeScript API and more examples:
typescript/README.md.
AKF is designed agent-first. One-line APIs for checking, stamping, streaming, and auditing.
AKF supports multi-agent orchestration β Claude Agent Teams, Copilot Cowork, Codex multi-agent, and any A2A-compatible platform.
CLI:
AKF ships an MCP server so any AI agent can create, validate, scan, and audit trust metadata.
11 MCP tools: check_file Β· replay_file Β· create_claim Β· validate_file Β· scan_file Β· trust_score Β· stamp_file Β· audit_file Β· embed_file Β· extract_file Β· detect_threats
AKF works where AI agents work. Drop a config file, and every AI-generated file carries trust metadata automatically.
| Agent | How it works |
|---|---|
| Claude Code | Plugin: /plugin marketplace add HMAKT99/AKF β /plugin install akf β auto-stamp hook + check skill. Or reads CLAUDE.md |
| Cursor | Reads .cursorrules β stamps AI edits before you review |
| Windsurf | Reads .windsurfrules β stamps AI edits with trust metadata |
| GitHub Copilot | Reads .github/copilot-instructions.md (native) + shell hook for CLI |
| OpenAI Codex | Reads AGENTS.md β stamps files in cloud sandbox and local |
| OpenClaw | Skill on ClawHub: clawhub install akf β check/stamp protocol + memory trust |
| Hermes Agent | agentskills.io skill: hermes skills tap add HMAKT99/AKF β files, memories, and skill supply-chain |
| Manus / Other Agents | MCP server + shell hook β works with any agent that supports MCP or CLI |
| Any MCP agent | 11 MCP tools β check, replay, stamp, audit, embed, extract, detect, validate, scan, trust, create |
| Any CLI tool | eval "$(akf shell-hook)" β intercepts claude, chatgpt, aider, openclaw, ollama, manus |
The trust pipeline:
Set up in 60 seconds:
AKF provides agent skill files that AI agents can discover and use. Drop these into your agent's context:
| Skill | What it does |
|---|---|
check.md | Check a file's trust before building on it |
stamp.md | Stamp trust metadata onto AI outputs |
audit.md | Audit files for regulatory compliance |
scan.md | Security scan files and directories |
embed.md | Embed trust metadata into Office/PDF/images |
detect.md | Run 10 security detection classes |
stream.md | Stream trust metadata in real-time |
git.md | Trust-annotated git workflows |
convert.md | Convert between formats |
delegate | Agent-to-agent trust delegation |
team | Multi-agent streaming sessions |
Compact (~15 tokens β optimized for AI):
Descriptive (human-readable β same data):
Full (with provenance, decay, AI flags, security):
AKF embeds natively β no sidecars needed for most formats:
| Format | How It Works |
|---|---|
.akf | Native standalone knowledge file |
.docx .xlsx .pptx | OOXML custom XML part |
.pdf | PDF metadata stream |
.html | JSON-LD <script type="application/akf+json"> |
.md | YAML frontmatter |
.png .jpg | EXIF/XMP metadata |
.json | Reserved _akf key |
.mp4 .mov .webm .mkv | Sidecar .akf.json companion |
.mp3 .wav .flac .ogg | Sidecar .akf.json companion |
| Everything else | Sidecar .akf.json companion |
AKF can automatically stamp every file AI touches β no manual intervention needed.
The background watcher monitors directories for new and modified files and stamps them with trust metadata. Smart context detection automatically infers:
git log history.akf/config.json rulesAutomatically detects when you run claude, chatgpt, aider, openclaw, ollama, or other AI CLI tools, and stamps any files they create or modify. Also pre-stamps files before upload to content platforms (gws, box, m365, dbxcli, rclone) so trust metadata travels with the file. Use --no-upload-hooks to disable.
Create .akf/config.json in your project root:
Files matching these patterns are automatically classified when stamped.
10 built-in detection classes: AI content without review, trust below threshold, hallucination risk, knowledge laundering, classification downgrade, stale claims, ungrounded AI claims, trust degradation chain, excessive AI concentration, provenance gap.
| Tier | Weight | Example |
|---|---|---|
| 1 | 1.00 | SEC filings, official records |
| 2 | 0.85 | Analyst reports, peer-reviewed |
| 3 | 0.70 | News, industry reports |
| 4 | 0.50 | Internal estimates, CRM data |
| 5 | 0.30 | AI inference, extrapolations |
Decision: score β₯ 0.7 β ACCEPT Β· β₯ 0.4 β LOW Β· < 0.4 β REJECT
Delegation ceiling: When an agent delegates to another, the delegate's output trust is capped at min(score, delegation_ceiling). This prevents trust inflation in multi-agent chains.
Framework integrations (install from repo via pip install ./packages/<name>):
| Package | Description |
|---|---|
mcp-server-akf | MCP server β create, validate, scan, trust |
langchain-akf | LangChain callback handler + document loader (experimental) |
llama-index-akf | LlamaIndex node parser + trust filter (experimental) |
crewai-akf | CrewAI tool for trust-aware agents (experimental) |
Editor & CI extensions (source in repo):
| Extension | Description |
|---|---|
| VS Code | Syntax highlighting, hover info, validation for .akf files |
| VS Code AI Monitor | Auto-stamp files edited by Copilot, Cursor, and other AI tools |
| GitHub Action | CI trust gate β runs akf certify on PRs with optional PR comments |
| Google Workspace | Add-on for Docs, Sheets, Slides (preview) |
| Office Add-in | Add-in for Word, Excel, PowerPoint (preview) |
Prompt with one example and LLMs produce valid AKF 95%+ of the time:
See LLM-PROMPT.md for a full system prompt.
| Doc | Description |
|---|---|
| Full Spec | Complete format specification |
| JSON Schema | Machine-readable schema |
| Producing AKF | Quick start for 8 languages |
| Trust Computation | Scoring algorithm details |
| Falsifiable Evidence | Replay recipes β re-run the probe, don't trust the label |
| Agent Memory | Trust-decayed memory stamps |
| Skill Provenance | Supply-chain trust for skill files |
| LLM Integration | Prompting strategies |
| EU AI Act | Compliance mapping |
| NIST AI RMF | Framework mapping |
| AKF | C2PA | Watermarking | Manual tracking | |
|---|---|---|---|---|
| Works on documents/code | β | β (media only) | β | β οΈ |
| No Certificate Authority needed | β | β | β | β |
| Trust scores | β | β | β | β |
| Source provenance chain | β | β | β | β οΈ |
| Compliance auditing | β | β | β | β |
| ~15 tokens (LLM-friendly) | β | β | N/A | N/A |
| 20+ file formats | β | β οΈ (media) | β οΈ (text) | β |
| Free & open source | β | β οΈ | Varies | β |
EU AI Act Article 50 takes effect August 2, 2026 β AI-generated content must carry transparency metadata (penalties up to EUR 35M / 7% of global turnover). Files stamped with AKF already carry it:
Mappings for EU AI Act and NIST AI RMF.
See CONTRIBUTING.md for development setup, testing, and PR process.
AKF is free and open source under the MIT license. The format specification will always be free. No feature will ever be gated behind a paid tier. AKF is a standard, and standards must be free to be universal.
MIT β use it everywhere, embed it in everything.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/akf)<a href="https://allmcps.com/mcp/akf"><img src="https://allmcps.com/api/badge/akf?style=directory" alt="Akf on AllMCPs" /></a>