SWT3 AI Witness runs on your own machine — the client starts it, so there is no endpoint to ping. 1 016 installs a week from npm. Last commit 27 Oct 2026.
Cryptographic AI governance and audit. 75 tools, 84 frameworks. EU AI Act, NIST, CMMC, MCP Top 10.
We read the source, 5 d ago · rules 995398eba69f
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)
"AC-2.1": "Found {factor_b} accounts with empty passwords. DISA STIG V-238196 (CAT I) requires zero empty-password accounts in /etc/shadow.",
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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": {
"command": "npx",
"args": [
"-y",
"@tenova/swt3-mcp"
]
}
}
}
[mcp_servers.swt3-witness]
command = "npx"
args = ["-y", "@tenova/swt3-mcp"]
{
"mcpServers": {
"swt3-witness": {
"command": "npx",
"args": [
"-y",
"@tenova/swt3-mcp"
]
}
}
}
{
"servers": {
"swt3-witness": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tenova/swt3-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
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).
Deterministic zero-trust policy enclave and cryptographic WORM audit ledger for MCP tools.
Financial governance for AI agents — spend gates and audit trail exposed as MCP tools.
Cryptographic audit trail for AI agents. Sign, verify, export. GDPR/HIPAA/EU AI Act.
Certainty for AI Agents. Deterministic MCP tools for dates, crypto, finance. 84 tools.
Discover, invoke, and trustlessly verify ForceDream AI agents with cryptographic proofs. 17 tools.
MCP server exposing Signet cryptographic signing, verification, and content hash tools over stdio.
Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance.
Production-grade cryptography toolkit with 31 MCP tools for classical, PQC, and KMS workflows.
Answers built from our own checks of this server.