VITNA – Containment for rogue AI agents MCP Server
by costrinityxyz.costrinity/vitna-compliance-preflightv0.5.4
Wraps stdio MCP servers. Risky calls wait for a person; no answer, no run. Signed records.
context tax
queued
security
queued
cold start
queued
freshness
Active3d ago
Install VITNA – Containment for rogue AI agents MCP server
Install in Claude Code
claude mcp add vitna-compliance -e VITNA_API_KEY='<vitna-api-key>' -- npx -y @costrinity/vitna-compliance-mcpInstall in Cursor
{
"mcpServers": {
"vitna-compliance": {
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
],
"env": {
"VITNA_API_KEY": "<vitna-api-key>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Install in Claude Desktop
{
"mcpServers": {
"vitna-compliance": {
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
],
"env": {
"VITNA_API_KEY": "<vitna-api-key>"
}
}
}
}Settings → Developer → Edit Config (claude_desktop_config.json), then restart.
Install in VS Code
{
"servers": {
"vitna-compliance": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
],
"env": {
"VITNA_API_KEY": "<vitna-api-key>"
}
}
}
}Add to .vscode/mcp.json in your workspace.
Install in Windsurf
{
"mcpServers": {
"vitna-compliance": {
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
],
"env": {
"VITNA_API_KEY": "<vitna-api-key>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json.
Configuration
| Variable | Required | Secret | Description |
|---|---|---|---|
| VITNA_OWNER_ID | — | — | Your VITNA operator UUID. Optional: if unset, the first tool call self-provisions a restricted trial key. The old VIGIL_OWNER_ID name is still accepted. |
| VITNA_API_KEY | — | yes | Your VITNA API key (new keys vitna_..., legacy vigil_... keys remain valid). Optional: self-provisioned if unset. The old VIGIL_API_KEY name is still accepted. |
| VITNA_EMAIL | — | — | Email to own the self-provisioned trial account. Optional: a throwaway is used if unset. It does not claim the account: claim it with GitHub or a passkey. The old VIGIL_EMAIL name is still accepted. |
| VITNA_BASE_URL | — | — | VITNA base URL; override only for self-hosted. The old VIGIL_BASE_URL name is still accepted. |
| VITNA_OPEN_CLAIM | — | — | Set to 1 to have the trial's claim link opened in your default browser when a trial starts. Either way the link is printed in the MCP server log, and the agent is never sent it. |
Remote endpoints
- streamable-http
https://vitna.costrinity.xyz/api/mcp
Freshness
Active — last maintenance signal 3d ago. The newest of the signals below sets the band.
Last commit (default branch)
2026-10-07 · 3d ago · GitHub
Latest release
2026-10-07 · 3d ago · GitHub · v0.5.2
Package published
no data · npm/PyPI
Registry entry updated
2026-10-07 · 3d ago · official registry · v0.5.4
FAQ
›How do I install the VITNA – Containment for rogue AI agents MCP server in Claude Code?
Run: claude mcp add vitna-compliance -e VITNA_API_KEY='<vitna-api-key>' -- npx -y @costrinity/vitna-compliance-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does VITNA – Containment for rogue AI agents require an API key?
Yes. It expects VITNA_API_KEY, of which 1 is a secret.
›Can I use VITNA – Containment for rogue AI agents as a remote (hosted) MCP server?
Yes — it offers both a hosted endpoint and a local stdio package.
›Is VITNA – Containment for rogue AI agents in the official MCP registry?
Yes, as xyz.costrinity/vitna-compliance-preflight.