Back to Browse

Swt3 Ai MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Cryptographic AI governance + audit. 33 tools, 36 frameworks. EU AI Act, NIST, OWASP, CMMC, SR 11-7

About

Cryptographic AI governance + audit. 33 tools, 36 frameworks. EU AI Act, NIST, OWASP, CMMC, SR 11-7

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 2 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

9 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

database

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

SWT3 API key (starts with axm_). Omit for zero-config demo mode.Required

Environment variable: SWT3_API_KEY

Your tenant identifierOptional

Environment variable: SWT3_TENANT_ID

Path to swt3.yaml config file for policy-as-codeOptional

Environment variable: SWT3_CONFIG_FILE

Data clearing level: 0=analytics, 1=standard, 2=sensitive, 3=classifiedOptional

Environment variable: SWT3_CLEARING_LEVEL

Agent identity for AI-ID.1 witnessingOptional

Environment variable: SWT3_AGENT_ID

HMAC-SHA256 signing key for non-repudiationRequired

Environment variable: SWT3_SIGNING_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-tenova-swt3-witness": {
      "env": {
        "SWT3_API_KEY": "your-swt3-api-key-here",
        "SWT3_AGENT_ID": "your-swt3-agent-id-here",
        "SWT3_TENANT_ID": "your-swt3-tenant-id-here",
        "SWT3_CONFIG_FILE": "your-swt3-config-file-here",
        "SWT3_SIGNING_KEY": "your-swt3-signing-key-here",
        "SWT3_CLEARING_LEVEL": "your-swt3-clearing-level-here"
      },
      "args": [
        "-y",
        "@tenova/swt3-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

SWT3 - Sovereign Witness Protocol for AI

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

npm PyPI npm downloads PyPI downloads License

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.

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 108 AI procedures spanning 56 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": 1,
  "anchor_fingerprint": "c059eb5938c0",
  "anchor_epoch": 1774800000,
  "fingerprint_timestamp_ms": 1774800000000,
  "ai_prompt_hash": "315f5bdb76d078c4",
  "ai_response_hash": "a1b2c3d4e5f60718",
  "ai_latency_ms": 842,
  "ai_model_id": "gpt-4o",
  "ai_context": {
    "provider": "openai",
    "guardrails": ["content-filter", "pii-redaction"]
  }
}

The anchor_fingerprint is computed from SHA256("WITNESS:{tenant}:{procedure}:{fa}:{fb}:{fc}:{ts}"). Anyone with the factors can independently verify the math. Trust is a vulnerability. Math is the remedy.

Clearing Levels

The clearing engine controls what leaves your infrastructure. Your code always gets the full response. Clearing only affects what reaches the witness ledger.

LevelNameOn the WireUse Case
0AnalyticsHashes + factors + model + provider + guardrailsInternal analytics
1StandardHashes + factors + model + providerDefault. Production apps
2SensitiveHashes + factors + model onlyHealthcare, legal, PII workloads
3ClassifiedNumeric factors only. Model ID hashed.Defense, air-gapped environments

At Level 1+, raw prompts and responses never leave your infrastructure.

SDKs

LanguagePackageInstall
Pythonswt3-aipip install swt3-ai
TypeScript@tenova/swt3-ainpm install @tenova/swt3-ai
Swiftswt3-aiSwift Package Manager
Rustswt3-aicargo add swt3-ai
C#swt3-aidotnet add package swt3-ai
Rubyswt3-aigem install swt3-ai
Kotlinswt3-aiGradle/Maven
MCP Server@tenova/swt3-mcpnpx @tenova/swt3-mcp

8 SDKs, identical fingerprints. 226 cross-language test vectors validated at build time.

Get Started

  1. Create a free account - instant API key, no credit card
  2. pip install swt3-ai or npm install @tenova/swt3-ai
  3. Wrap your AI client. Every inference is witnessed.

Regulatory Coverage

FrameworkCoverage
EU AI ActArticles 9, 10, 12, 13, 14, 15, 50, 51, 53, 72
NIST AI RMFGOVERN, MAP, MEASURE, MANAGE (10 subcategories)
NIST 800-53SI-7, AU-2, AU-3, AC controls
CMMC v2.0Level 2 practice mappings
SR 11-7Model Risk Management (5 examination areas)
ISO 42001Annex A AI management controls

Repository Structure

packages/swt3-ai/        Python SDK (PyPI: swt3-ai)
packages/swt3-ai-ts/     TypeScript SDK (npm: @tenova/swt3-ai)
packages/swt3-ai-swift/  Swift SDK (Swift Package Index)
packages/swt3-ai-rust/   Rust SDK (crates.io: swt3-ai)
packages/swt3-ai-dotnet/ C# SDK (NuGet: swt3-ai)
packages/swt3-ai-ruby/   Ruby SDK (RubyGems: swt3-ai)
packages/swt3-ai-kotlin/ Kotlin SDK (Maven Central: io.tenova:swt3-ai)
packages/swt3-mcp/       MCP Server (npm: @tenova/swt3-mcp)
packages/swt3-witness/   K8s DaemonSet (GHCR + Helm)
packages/libswt3/        Protocol reference implementation
config/                  Control definitions and framework crosswalks

Compliance & Privacy

Your prompts and responses never leave your infrastructure. The SDK computes SHA-256 hashes locally and transmits only irreversible hashes and numeric factors to the witness ledger. At Clearing Level 3, even the model name is hashed.

Documentation

Contributing

See CONTRIBUTING.md for development setup and guidelines.

License

Apache 2.0. See LICENSE. Patent pending.


If you believe AI systems should prove they followed the rules, give us a star.

SWT3: Sovereign Witness Traceability. We don't run your models. We witness them.

TeNova - Defining the AI Accountability Standard.

Reviews

No reviews yet

Be the first to review this server!