Audifact MCP Server

Install Audifact MCP server

claude mcp add --transport http audifact-plugin https://api.audifact.io/mcp

{
  "mcpServers": {
    "audifact-plugin": {
      "url": "https://api.audifact.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "audifact-plugin": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.audifact.io/mcp"
      ]
    }
  }
}

{
  "servers": {
    "audifact-plugin": {
      "type": "http",
      "url": "https://api.audifact.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "audifact-plugin": {
      "serverUrl": "https://api.audifact.io/mcp"
    }
  }
}

Context tax

Connecting this server adds ~1,765 tokens of tool definitions to every model turn (moderate, 5 tools). Measured 2026-10-19 via its hosted endpoint; o200k tokenizer, worst case for clients that load all tools up front. How we measure

Input prices as of 2026-10-06. Excludes your own prompt and output.

Tools (5)

• log_decision583 tok

  Log a signed decision event to the ledger. Managed Mode (default for MCP): omit signing fields and pass agent_name - Audifact securely manages an Ed25519 keypair and signs on behalf of the agent. Events are immutable once recorded; managed mode provides strong auditability after receipt. For maximum provenance, use client-side signing via the SDK (agent_private_key_b64, or agent_public_key + signature). Linked outcomes must use the same signing method as the decision (managed or client-signed with the same agent key). Organization is always taken from the API key (do not send organization_id).

• log_outcome385 tok

  Log a signed outcome event linked to a prior decision via decision_event_hash. Managed Mode (default): omit signing fields - the managed key from the linked decision's agent is used automatically when the decision was also managed. For client-signed decisions, pass agent_private_key_b64 or agent_public_key + signature using the same agent key. Signing method must match the linked decision (managed or client-signed). Outcomes do not accept scenario fields - scenario context is inherited from the linked decision.

• list_agent_decisions322 tok

  List decision events for one agent (by public key) in the API key's org, newest first by default. When to use: to review what an agent already logged, pick an event_hash for get_proof, or page through history before linking an outcome. When NOT to use: to fetch one event's trust/anchor proof (use get_proof); to write a new decision or outcome (use log_decision / log_outcome); this is org-scoped via X-API-Key (not a public explorer listing) and does not accept agent_name — pass the agent's public_key from a prior log_decision response or register_agent. Requires X-API-Key. Read-only. Unknown pu

• get_proof229 tok

  Fetch the public proof payload for one ledger event by its 64-char hex event_hash. When to use: after log_decision/log_outcome when you need trust labels, chain validity, anchor status, or a paired-event proof URL. When NOT to use: to browse many decisions — use list_agent_decisions first, then call get_proof on a chosen event_hash; do not use this to write events (use log_decision / log_outcome). Requires X-API-Key. Returns proof fields only for events in that key's org; unknown or other-org hashes return EVENT_NOT_FOUND (same message either way). Read-only; does not mutate the ledger. Respon

• register_agent198 tok

  Register or look up an agent identity under the API key's organization. When to use: before client-side signing flows that need a known public_key, or to attach a human-readable name to an existing key. When NOT to use: Managed Mode log_decision (pass agent_name instead — Audifact provisions the key); do not use this to log decisions or outcomes. Idempotent on public_key: repeating the same key returns the existing agent. Requires X-API-Key. Returns the agent record (id, public_key, name).

Security signals

92/100 — no known issues found as of 2026-10-19, from the checks below. This is not a guarantee of safety; review what a server can do before connecting it.

Scan it yourself before installing with vectra-guard, the open-source agent security CLI. Scoring rules

Freshness

Active — last maintenance signal 2d ago. The newest of the signals below sets the band.

1. Last commit (default branch)

   2026-10-16 · 2d ago · GitHub

2. Latest release

   no data · GitHub

3. Package published

   no data · npm/PyPI

4. Registry entry updated

   2026-10-16 · 2d ago · official registry · v0.1.0