Loading
SWT3 AI Witness
io.tenovaClaim this server
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
npx -y @tenova/[email protected]Credentials from the publisher
- 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
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
SWT3_API_KEY=<secret> SWT3_TENANT_ID=<value> SWT3_CONFIG_FILE=<value> SWT3_CLEARING_LEVEL=<value> SWT3_AGENT_ID=<value> SWT3_SIGNING_KEY=<secret> claude mcp add io.tenova-swt3-witness -- npx -y @tenova/swt3-mcp@0.7.5Run in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.tenova-swt3-witness": { "command": "npx", "args": [ "-y", "@tenova/[email protected]" ], "env": { "SWT3_API_KEY": "<secret>", "SWT3_TENANT_ID": "<value>", "SWT3_CONFIG_FILE": "<value>", "SWT3_CLEARING_LEVEL": "<value>", "SWT3_AGENT_ID": "<value>", "SWT3_SIGNING_KEY": "<secret>" } } }}claude_desktop_config.json
Local · npmPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Local- Transport
- stdio
- Version
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ