Few Servers

Home›MCP servers›Security and compliance

VITNA – Containment for rogue AI agents MCP server

Remotenpm

VC · placeholder image
Placeholder. No logo or screenshot has been supplied for this listing yet.

Do you maintain this server? Claim this listing to add a logo or screenshot and to correct or extend it. Free, and a person checks every claim.

Claim this listingSuggest a correctionRatings and reviews

What it does

Wraps stdio MCP servers. Risky calls wait for a person; no answer, no run. Signed records.

Description as published by the publisher in the official MCP Registry, read 10 Oct 2026. Not written or verified by Few Servers.

Facts

Registry namexyz.costrinity/vitna-compliance-preflight
Publishercostrinity.xyz Namespace verified by the registry through the publisher's domain.
CategorySecurity and compliance sorted by our keyword rules
Transportremote (streamable-http), local package (npm)
Version0.5.4
This version published7 Oct 2026
Last seen10 Oct 2026, in our crawl of the official MCP Registry
Tested by Few ServersNo

Install

  • Remote endpoint (streamable-http), as published: https://vitna.costrinity.xyz/api/mcp
  • npm package, as published: @costrinity/vitna-compliance-mcp · version 0.5.5 · transport stdio
    npx -y @costrinity/vitna-compliance-mcp
    Standard run command for npm packages. The registry publishes the package name, not a command; check the repository for required arguments.

Install details read from the registry record on 12 Oct 2026. We have not run this server.

Keys and settings

The registry record declares a secret value (a key or token) that is not marked required. Declared by the publisher:

  • Authorization (header, secret, not marked required): 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 http
  • VITNA_OWNER_ID (environment variable, not marked required): 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 (environment variable, secret, not marked required): 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 (environment variable, not marked required): 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 o
  • VITNA_BASE_URL (environment variable, not marked required): VITNA base URL; override only for self-hosted. The old VIGIL_BASE_URL name is still accepted.
  • VITNA_OPEN_CLAIM (environment variable, not marked required): 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

RepositoryWebsiteRegistry record (JSON)npm package

Being listed is not a safety check. Read the repository and check what a server asks for before you connect it. How the directory works.

Ratings and reviews

No reviews yet.