Audit Ledger MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add audit-ledger-mcp -- npx -y audit-ledger-mcp

{
  "mcpServers": {
    "audit-ledger-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "audit-ledger-mcp"
      ]
    }
  }
}

[mcp_servers.audit-ledger-mcp]
command = "npx"
args = ["-y", "audit-ledger-mcp"]

{
  "mcpServers": {
    "audit-ledger-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "audit-ledger-mcp"
      ]
    }
  }
}

{
  "servers": {
    "audit-ledger-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "audit-ledger-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: AUDIT_API_URL (Your deployed audit-ledger API endpoint (e.g. https://<api-id>.execute-api.<region>.amazonaws.com/prod). Leave unset to run in sandbox mode against the public shared tenant), AUDIT_WRITE_KEY (Tenant write key for your deployed ledger. Required if AUDIT_API_URL is set and you want to call record_decision), AUDIT_READ_KEY (Tenant read key for your deployed ledger. Required if AUDIT_API_URL is set and you want to call verify_decision or list_decisions), AUDIT_TIMEOUT_MS (HTTP timeout in milliseconds. Defaults to 5000), AUDIT_RETRY_ATTEMPTS (Number of retry attempts on transient failures. Defaults to 3), AUDIT_HMAC_KEY (Tenant secret used to HMAC-SHA256 PII and prompts locally before sending. Generate once per tenant (e.g. node -e "console.log(require('crypto').randomBytes(32).toString('hex'))") and keep it in your environment. The key never leaves your process. If unset, the MCP falls back to plain SHA-256 for backwards compatibility and logs a one-time deprecation warning; set this to switch to keyed hashing, which regulators (ICO/EDPB) expect for pseudonymisation).