Hybrid
VITNA – Containment for rogue AI agents
Guard wraps stdio MCP servers: risky calls wait for a person; no answer, no run. Remote: cooperative
xyz.costrinity/vitna-compliance-preflightSource repository
Overview
What this server provides
Guard wraps stdio MCP servers: risky calls wait for a person; no answer, no run. Remote: cooperative
Connect
1Remote endpoints
https://vitna.costrinity.xyz/api/mcp- AuthorizationOptional
Bearer <your VITNA API key>. Discovery (initialize, tools/list) and vitna_help work without it; every governed decision tool requires it. Get a key free at https://vitna.costrinity.xyz/dashboard. X-API-Key is also accepted.
Install
1Packages
@costrinity/vitna-compliance-mcp0.5.6
Runtime
Not declaredTransport stdio- VITNA_OWNER_IDOptional
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_KEYOptional
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_EMAILOptional
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_URLOptional
VITNA base URL; override only for self-hosted. The old VIGIL_BASE_URL name is still accepted.
Default: https://vitna.costrinity.xyz - VITNA_OPEN_CLAIMOptional
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.