Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Akf

by HMAKT99version 1.6.2i★ –iRuns on your computer
Registry nameio.github.HMAKT99/akf

Install

Overview

Description from the maker (original English)

Trust metadata for AI agents — check files before building on them, stamp verified work.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "akf": {
      "command": "uvx",
      "args": [
        "mcp-server-akf"
      ]
    }
  }
}

Run this in your terminal

claude mcp add akf -- uvx mcp-server-akf

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "akf": {
      "command": "uvx",
      "args": [
        "mcp-server-akf"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "akf": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-server-akf"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account HMAKT99, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32727 servers in this category
  • Published to the registry more recently than 73% of the other 32727 servers in this category
  • Basic checks equal to or better than 100% of the other 32727 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Akf safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.6.2) reached the registry 14 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Foliosio

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Foliosio

by foliosio.com

Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-server-akf

mcp-name: io.github.HMAKT99/akf

MCP (Model Context Protocol) server that exposes 10 AKF tools to AI agents. Any MCP-compatible client (Claude Desktop, Claude Code, Cursor, Windsurf, etc.) can check, stamp, validate, audit, and scan files using the Agent Knowledge Format.

A stamp costs ~15 tokens. Re-verifying costs 15,000. Agents stamp what they verify; the next agent calls check_file and builds on it instead of redoing the work.

Installation

pip install mcp-server-akf

Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{

"mcpServers": { "akf": { "command": "python", "args": ["-m", "mcp_server_akf"] } } }

Cursor

Add to .cursor/mcp.json in your project root:

{

"mcpServers": { "akf": { "command": "python", "args": ["-m", "mcp_server_akf"] } } }

Tools

ToolDescription
check_fileOne-line trust check — can an agent build on this file without re-verifying? (OK / LOW / STALE / UNSTAMPED)
create_claimCreate an AKF claim with trust metadata
validate_fileValidate an .akf file against the spec
scan_fileSecurity scan any file for AKF metadata
trust_scoreCompute effective trust score for a claim
stamp_fileStamp trust metadata onto any file (20+ formats)
audit_fileCompliance audit (EU AI Act, SOX, HIPAA, GDPR, NIST, ISO 42001)
embed_fileEmbed AKF metadata into DOCX, PDF, HTML, images, etc.
extract_fileExtract AKF metadata from any supported format
detect_threatsRun 10 AI-specific security detections

Quick usage

Once configured, ask your AI agent:

"Stamp report.docx with AKF trust metadata, confidence 0.9, evidence 'quarterly review complete'"

The agent will call stamp_file through MCP and attach provenance automatically.

You can also run the server directly for testing:

python -m mcp_server_akf

Verification state in tool results (experimental)

On mcp 2.x, a tool result for a file (any tool called with path) carries that file's verification state in _meta under the vendor key dev.akf/trust:

"_meta": {

"dev.akf/trust": { "v": "1", "status": "OK", "trust": 0.7447, "evidence": ["human_review"], "agent": "claude-code", "age_days": 4 } }

status is computed live (OK / LOW / STALE / UNSTAMPED), so a client sees whether the file changed since it was verified. The key is absent when the result isn't about a file. Clients that don't know the key ignore it.

To annotate your own server's results:

from mcp_server_akf.meta import TRUST_META_KEY, trust_meta

meta = trust_meta(path) return CallToolResult(content=[...], _meta={TRUST_META_KEY: meta} if meta else None)

To read it in a client:

result = await client.call_tool("extract_file", {"path": "report.md"})

state = (result.meta or {}).get("dev.akf/trust") if state and state["status"] == "OK": ... # verified and unchanged: build on it without re-verifying

Multi-Agent Support

The MCP server works seamlessly with multi-agent orchestration platforms:

  • Agent Identity: Create and verify agent cards via akf agent create / akf agent verify
  • A2A Protocol: Export/import agent cards for cross-platform discovery via akf agent export-a2a
  • Team Certification: Use akf certify --team for per-agent trust breakdowns in CI
  • Delegation: Trust ceilings cap delegate output when agents hand off work
  • Team Streaming: Multi-agent sessions with per-agent claim attribution

Supports: Claude Agent Teams, Copilot Cowork, Codex multi-agent, and any A2A-compatible platform.

Requirements

  • Python >= 3.10
  • akf >= 1.0.0
  • mcp >= 1.0.0
Ask PopNx