VITNA – Containment for rogue AI agents MCP Server

Guard wraps stdio MCP servers: risky calls wait for a person; no answer, no run. Remote: cooperative

Local + remotestreamable-httpstdio

What is the VITNA – Containment for rogue AI agents MCP Server?

VITNA – Containment for rogue AI agents is an MCP integration. Guard wraps stdio MCP servers: risky calls wait for a person; no answer, no run. Remote: cooperative.

Hosted connection

The registry lists a streamable-http connection at https://vitna.costrinity.xyz/api/mcp. The endpoint declares these request headers: Authorization.

Packages and local setup

The published npm package is @costrinity/vitna-compliance-mcp, version 0.5.6. Its declared MCP transport is stdio.

The package declares 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: 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.5.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related legal & compliance MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
VITNA_OWNER_IDYour 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.Check documentation
VITNA_API_KEYYour 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.Check documentation
VITNA_EMAILEmail 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.Check documentation
VITNA_BASE_URLVITNA base URL; override only for self-hosted. The old VIGIL_BASE_URL name is still accepted.Check documentation
VITNA_OPEN_CLAIMSet 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.Check documentation