Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

SWT3 AI Witness

✓ tenova.io

by tenova-labsversion 8.1.0i★ 0iRuns on your computerOfficial site ↗
Registry nameio.tenova/swt3-witness

How to install

What it does

Cryptographic AI governance and audit. 75 tools, 98 frameworks. EU AI Act, NIST, CMMC, MCP Top 10.

  • Connects Runs on your computer
  • Account or key Needs SWT3_API_KEY, SWT3_SIGNING_KEY
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity16/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score28/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

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

Let your AI install it with one sentence

Please install SWT3 AI Witness. Follow https://mcp.popnx.com/i/tenova-swt3-witness.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SWT3 AI Witness for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "swt3-witness": { "command": "npx", "args": [ "-y", "@tenova/swt3-mcp" ], "env": { "SWT3_API_KEY": "your-value", "SWT3_SIGNING_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SWT3_API_KEY, SWT3_SIGNING_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SWT3 AI Witness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SWT3 AI Witness key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SWT3 AI Witness site ↗

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "swt3-witness": {
          "command": "npx",
          "args": [
            "-y",
            "@tenova/swt3-mcp"
          ],
          "env": {
            "SWT3_API_KEY": "your-value",
            "SWT3_SIGNING_KEY": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use SWT3 AI Witness and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using SWT3 AI Witness or shows a SWT3 AI Witness tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect SWT3 AI Witness yet

SWT3 AI Witness runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect SWT3 AI Witness

  • You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SWT3 AI Witness for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user swt3-witness --env SWT3_API_KEY=your-value --env SWT3_SIGNING_KEY=your-value -- npx -y @tenova/swt3-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SWT3_API_KEY, SWT3_SIGNING_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SWT3 AI Witness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SWT3 AI Witness key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SWT3 AI Witness site ↗

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user swt3-witness --env SWT3_API_KEY=your-value --env SWT3_SIGNING_KEY=your-value -- npx -y @tenova/swt3-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see SWT3 AI Witness listed as connected

  6. Try it

    Use SWT3 AI Witness and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using SWT3 AI Witness or shows a SWT3 AI Witness tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SWT3 AI Witness for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "swt3-witness": { "command": "npx", "args": [ "-y", "@tenova/swt3-mcp" ], "env": { "SWT3_API_KEY": "your-value", "SWT3_SIGNING_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SWT3_API_KEY, SWT3_SIGNING_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SWT3 AI Witness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SWT3 AI Witness key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SWT3 AI Witness site ↗

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the SWT3 AI Witness settings, SWT3_API_KEY, SWT3_SIGNING_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use SWT3 AI Witness and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using SWT3 AI Witness or shows a SWT3 AI Witness tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a SWT3 AI Witness key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SWT3 AI Witness for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "swt3-witness": { "type": "stdio", "command": "npx", "args": [ "-y", "@tenova/swt3-mcp" ], "env": { "SWT3_API_KEY": "your-value", "SWT3_SIGNING_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SWT3_API_KEY, SWT3_SIGNING_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SWT3 AI Witness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SWT3 AI Witness key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SWT3 AI Witness site ↗

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the SWT3 AI Witness settings, SWT3_API_KEY, SWT3_SIGNING_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use SWT3 AI Witness and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using SWT3 AI Witness or shows a SWT3 AI Witness tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use SWT3 AI Witness💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user swt3-witness --env SWT3_API_KEY=your-value --env SWT3_SIGNING_KEY=your-value -- npx -y @tenova/swt3-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "swt3-witness": {
      "command": "npx",
      "args": [
        "-y",
        "@tenova/swt3-mcp"
      ],
      "env": {
        "SWT3_API_KEY": "your-value",
        "SWT3_SIGNING_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "swt3-witness": {
      "command": "npx",
      "args": [
        "-y",
        "@tenova/swt3-mcp"
      ],
      "env": {
        "SWT3_API_KEY": "your-value",
        "SWT3_SIGNING_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "swt3-witness": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@tenova/swt3-mcp"
      ],
      "env": {
        "SWT3_API_KEY": "your-value",
        "SWT3_SIGNING_KEY": "your-value"
      }
    }
  }
}

Values you fill in

  • SWT3_API_KEY secret required env
    SWT3 API key (starts with axm_). Omit for zero-config demo mode.
  • SWT3_TENANT_ID env
    Your tenant identifier
  • SWT3_CONFIG_FILE env
    Path to swt3.yaml config file for policy-as-code
  • SWT3_CLEARING_LEVEL env
    Data clearing level: 0=analytics, 1=standard, 2=sensitive, 3=classified
  • SWT3_AGENT_ID env
    Agent identity for AI-ID.1 witnessing
  • SWT3_SIGNING_KEY secret required env
    HMAC-SHA256 signing key for non-repudiation

Descriptions are as written by the maker.

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

At a glance

Downloads per weeki
510/wk
Verified domain
✓ tenova.io
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
8.1.0
Categoryi
Other
Published to registryi
Nov 11, 2026
Code last changedi
Nov 17, 2026
Maker
tenova-labs
Packages
npm: @tenova/swt3-mcp
Website
tenova.io
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

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 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain tenova.io (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed 2 days ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – 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

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @tenova/swt3-mcp@8.1.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/tenova-swt3-witness.svg)](https://mcp.popnx.com/en/servers/tenova-swt3-witness)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20815 servers in this category
  • Published to the registry more recently than 84% of the other 20815 servers in this category
  • Basic checks equal to or better than 99% of the other 20815 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 SWT3 AI Witness safe?

It passed 3 of 3 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?

You need to fill in: SWT3_API_KEY, SWT3_SIGNING_KEY

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 2 days ago, and the latest version (8.1.0) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
SWT3 AI Witness
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseApache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

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.

SWT3 - Sovereign Witness Protocol for AI

Don't audit the agent's thoughts. Audit the agent's actions.

The Problem

AI agents are making production decisions: approving loans, triaging patients, managing infrastructure, writing code. In 2026, 65% of firms reported AI agent security incidents. Only 14.4% of agents go live with full security approval. When something goes wrong, there is no tamper-proof audit trail. Logs are mutable. Metrics are averaged. Nobody can prove what the agent actually did.

GPAI transparency obligations are enforceable now. EU AI Act high-risk enforcement begins December 2, 2027. NIST AI RMF, SR 11-7, and CMMC impose similar obligations. 72% of enterprises believe they have AI governance but lack actual control. Most teams have nothing but dashboards and hope.

The Protocol

SWT3 (Sovereign Witness Traceability) is a deterministic witness protocol for AI systems. It intercepts AI actions, hashes the evidence, and anchors cryptographic proof to an immutable ledger. Your code gets the full response. The auditor gets tamper-proof evidence. Raw prompts and responses never leave your infrastructure.

  • Deterministic, not probabilistic. The witness engine uses fixed logic, not AI, to evaluate compliance.
  • Zero data retention. Configurable clearing levels strip sensitive content before it leaves your environment.
  • Framework-mapped. Every anchor maps to EU AI Act articles, NIST AI RMF functions, and federal controls.

What's New in v8.2

v8.2.0 is the Terraform Enterprise Deployment release. SWT3 now deploys into AWS, Azure, and GCP with native infrastructure-as-code modules, production-grade observability, and zero-SDK witnessing for teams that cannot modify application code.

5 Terraform Modules -- Infrastructure witnesses that read cloud audit logs (CloudTrail, Activity Log, Cloud Audit Log), extract canonical fields, compute deterministic hashes, and anchor them via the SWT3 protocol. Raw audit data never leaves your cloud account.

ModuleCloudPattern
aws-lambda-cloudtrailAWSS3 -> SQS -> Lambda
aws-ecs-sidecarAWSECS task sidecar container
aws-eks-daemonsetAWSHelm DaemonSet on every EKS node
azure-functionAzureEvent Grid -> Function
gcp-cloud-functionGCPLog Router -> Pub/Sub -> Function

5 New CLI Commands -- swt3 verify-chain (local chain integrity verification with tamper detection), swt3 mock-server (local test endpoint returning SWT3-MOCK- anchors), swt3 profile list|show|compare (governance profile management), swt3 upgrade (version check against PyPI/npm).

Passive Tail Sidecar -- Log-based witnessing for the 50-microservice problem. A sidecar container reads structured JSON logs via shared volume mount and witnesses them without any SDK integration. One kubectl apply adds governance to every pod in a namespace.

Kustomize Sidecar Overlay -- For teams that do not use Helm, a Kustomize overlay injects the witness sidecar into existing deployments with kustomize build.

CloudWatch and Prometheus Alarms -- PrometheusRule for witness anchor drift, CloudWatch alarms for Lambda error rate, SQS dead-letter depth, and invocation throttling. SRE runbook included.

Docker Compose Dev Environment -- docker compose up spins up a local witness endpoint, mock receiver, and Prometheus/Grafana stack for development and integration testing.

Why This Matters

Enterprise AI governance has a last-mile problem. The SDK covers application code, but regulated infrastructure -- CloudTrail events, container orchestration, serverless functions, hardware attestation -- requires a different deployment model. Teams running 50+ microservices cannot add SDK calls to every service. Platform engineers need Terraform modules, not code changes.

v8.2 closes this gap. A platform team can terraform apply a CloudTrail witness, kubectl apply a Kustomize sidecar overlay, and get continuous compliance evidence from infrastructure that was previously unmonitored. Combined with the existing SDK and K8s DaemonSet, SWT3 now witnesses AI governance from silicon to serverless in a single protocol.

Try It (10 Seconds, No Account)

Python

pip install swt3-ai

python -m swt3_ai.demo

TypeScript

npm install @tenova/swt3-ai

npx swt3-demo

No API keys. No account. No network calls. You will see the full witnessing pipeline run locally.

Three Lines to Production

from swt3_ai import Witness

from openai import OpenAI

witness = Witness(endpoint="https://sovereign.tenova.io", api_key="axm_live_...", tenant_id="YOUR_TENANT") client = witness.wrap(OpenAI())

Every inference is now witnessed. Your code does not change.

response = client.chat.completions.create( model="gpt-4o", messages=[{"role": "user", "content": "Summarize this contract"}], )

Works with OpenAI, Anthropic, AWS Bedrock, Vercel AI SDK, LangChain, LiteLLM (100+ providers), and any OpenAI-compatible endpoint (vLLM, Ollama, Azure OpenAI).

K8s Hardware Attestation

AI compliance doesn't stop at the model layer. Regulators want to know what hardware ran the inference, whether it was authorized, and whether the compute environment changed between audit periods. Today, no platform provides cryptographic proof of which silicon processed which workload. SWT3 does.

Deploy a DaemonSet that discovers accelerator hardware on every node and mints AI-HW.1 attestation anchors. Zero application code changes. One Helm install.

helm install swt3-witness oci://ghcr.io/tenova-labs/charts/swt3-witness \

--set config.endpoint="https://sovereign.tenova.io" \ --set config.apiKey="axm_live_..." \ --set config.tenantId="YOUR_TENANT"

The DaemonSet auto-discovers 6 accelerator types per node:

Discovery PathSiliconMethod
NVIDIA GPUA100, H100, H200, B200, GB200, NVL72nvidia-smi
Google TPUv4, v5e, v5p, v6e, TrilliumTPU_NAME env
AMD MIMI300X, MI325X, MI250rocm-smi
AWS TrainiumTrainium2, Inferentia2neuron-ls
Intel GaudiGaudi3, Gaudi2hl-smi
PCI FallbackAny 3D controller / processing accelerator/sys/bus/pci

Each node reports its silicon vendor, topology, memory, and per-accelerator detail. Non-accelerator nodes produce a valid anchor attesting "no accelerator detected" -- absence of hardware is also auditable evidence. Mixed-silicon clusters (NVIDIA + TPU + AMD in the same cluster) are fully supported.

What this proves to your auditor:

  • Which hardware ran each AI workload (EU AI Act Art. 15(4), NIST 800-53 SI-7)
  • Whether the compute environment changed between assessments (drift detection)
  • That inference didn't silently migrate to unauthorized or unqualified silicon
  • Full hardware provenance from silicon to model, combined with AI-HW.3 (TPM attestation)

The witness context includes silicon_vendor, discovery_method, and accelerators[]. All device identifiers are SHA-256 hashed before leaving the node. Serial numbers, UUIDs, and bus IDs are never transmitted in plaintext.

See the Cross-Silicon K8s Attestation Guide for GKE, EKS, AKS, and on-prem deployment patterns.

What Gets Witnessed

Each inference produces anchors across 145 AI procedures spanning 10 namespaces:

ProcedureDomainWhat It ProvesRegulatory Mapping
AI-INF.1InferencePrompt and response captured (provenance)EU AI Act Art. 12
AI-INF.2InferenceLatency within threshold (detects model swaps)NIST AI RMF MEASURE 2.6
AI-MDL.1ModelDeployed model matches approved hash (integrity)EU AI Act Art. 9
AI-MDL.2ModelModel version identifier recorded (tracking)EU AI Act Art. 72
AI-MDL.5ModelWeight file SHA-256 verified (tamper detection)EU AI Act Art. 15(4)
AI-MDL.6ModelLoRA/PEFT adapter stack attestedEU AI Act Art. 12(2)(b)
AI-MDL.7ModelQuantization method recordedEU AI Act Art. 15(3)
AI-GRD.1GuardrailRequired safety filters were active (enforcement)NIST AI RMF GOVERN 1.5
AI-GRD.2SafetyNo content filter or refusal triggeredEU AI Act Art. 14
AI-GRD.3GatekeeperPre-call guardrail gate enforcedEU AI Act Art. 9(2)
AI-RAG.1RetrievalRAG context chunks and corpus attestedEU AI Act Art. 12(2)(a)
AI-RAG.2RetrievalRetrieval relevance scoring verifiedEU AI Act Art. 10(2)
AI-TOOL.1Tool UseAgent tool/function call recorded (latency, success)NIST AI RMF MANAGE 4.1
AI-ID.1IdentityWitness instance identity attested (agent accountability)EU AI Act Art. 13
AI-ACC.1AccessResource access granted or denied with scopeEU AI Act Art. 9(4)(c)
AI-REV.1RevocationPreviously-issued anchor revoked with reasonEU AI Act Art. 12(3)
AI-SEC.1SecurityAdversarial threat detection performedEU AI Act Art. 15(4)
AI-SEC.2SecurityInput validated and sanitized before inferenceEU AI Act Art. 15(3)
AI-SKILL.1SkillsLoaded skill/tool/plugin manifest attestedEU AI Act Art. 12(2)(b)
AI-SKILL.2MemoryActive memory sources bound to decisionEU AI Act Art. 12(2)(a)
AI-SKILL.3AlignmentRLHF/DPO reward model binding recordedEU AI Act Art. 9(4)(a)
AI-CHAIN.1ChainMulti-agent handoff witnessed with cycle trackingEU AI Act Art. 12(2)(a)
AI-VIO.1ViolationPolicy violation detected during inferenceEU AI Act Art. 9(4)(a)
AI-CHR.1CharterAgent charter/system prompt hash attestedEU AI Act Art. 13
AI-MDL.8ModelModel verified against approved registryEU AI Act Art. 51
AI-HITL.3OversightReviewer identity bound to human reviewEU AI Act Art. 12(3)(d)
AI-SAFE.1SafetyStop mechanism tested, safe state confirmedEU AI Act Art. 14(4)(e)
AI-HW.1HardwareGPU/accelerator inventory attested at startupEU AI Act Art. 15(4)
AI-TRUST.1TrustMutual compliance trust verified between agentsEU AI Act Art. 9(4)(c)
AI-TRUST.2TrustTrust handshake details recordedEU AI Act Art. 12(2)(a)
AI-MARK.1ContentContent provenance marking attestedEU AI Act Art. 50(2)
AI-BASE.1BaselineAgent behavioral baseline monitoredNIST AI RMF MEASURE 2.6
AI-ENV.1EnvironmentRuntime environment fingerprint recordedEU AI Act Art. 15(4)
AI-ENV.2EnvironmentDependency manifest attestedEU AI Act Art. 15(3)
AI-DATA.3DataTraining data lineage attestedEU AI Act Art. 10(2)
AI-DATA.4DataData quality metrics recordedEU AI Act Art. 10(3)
AI-CHAIN.2ChainChain-of-trust credential verifiedEU AI Act Art. 9(4)(c)

Plus 70 additional procedures covering fairness, explainability, inference volume, model drift, human oversight, cybersecurity, supply chain, content marking, agent lifecycle, financial transactions, and cross-border routing. See the full procedure registry.

View an Anchor

A Level 1 anchor for AI-INF.1 (Inference Provenance). This is what reaches the witness ledger. No prompts, no responses, just cryptographic proof.

{

"procedure_id": "AI-INF.1", "factor_a": 1, "factor_b": 1, "factor_c": 0, "clearing_level":

Only the beginning is shown; read the rest in the repo