SWT3 AI Witness MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    command: "find /etc/cron.d /etc/cron.daily /etc/cron.hourly /etc/cron.weekly /etc/cron.monthly -type f 2>/dev/null | wc -l"

      if (existsSync("/.dockerenv") || existsSync("/run/.containerenv")) {

        filepath = os.path.join(handoff_path, filename)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

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 swt3-witness -- npx -y @tenova/swt3-mcp

{
  "mcpServers": {
    "swt3-witness": {
      "args": [
        "-y",
        "@tenova/swt3-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.swt3-witness]
command = "npx"
args = ["-y", "@tenova/swt3-mcp"]

{
  "mcpServers": {
    "swt3-witness": {
      "args": [
        "-y",
        "@tenova/swt3-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "swt3-witness": {
      "args": [
        "-y",
        "@tenova/swt3-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SWT3_API_KEY (SWT3 API key (starts with axm_). Omit for zero-config demo mode.), SWT3_TENANT_ID (Your tenant identifier), SWT3_CONFIG_FILE (Path to swt3.yaml config file for policy-as-code), SWT3_CLEARING_LEVEL (Data clearing level: 0=analytics, 1=standard, 2=sensitive, 3=classified), SWT3_AGENT_ID (Agent identity for AI-ID.1 witnessing), SWT3_SIGNING_KEY (HMAC-SHA256 signing key for non-repudiation). The author declared them in the registry entry; get the values from the project itself.