VITNA – Containment for rogue AI agents

Name: VITNA – Containment for rogue AI agents
Author: xyz.costrinity

MCP serverMCP

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

by xyz.costrinityrepository ↗homepage ↗v0.5.4MIT

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"costrinity-vitna-compliance-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability74/79 checks ok

when	check	result	http	latency	detail
26 h ago	http head	failed	—	—	disallowed by robots.txt
5 d ago	http head	failed	—	—	disallowed by robots.txt
8 d ago	http head	failed	—	—	disallowed by robots.txt
9 d ago	http head	failed	—	—	disallowed by robots.txt
9 d ago	http head	failed	—	—	disallowed by robots.txt
9 d ago	mcp initialize	ok	200	919 ms	server vitna-compliance 0.5.0 · protocol 2025-03-26 · 23 tools
10 d ago	mcp initialize	ok	200	176 ms	server vitna-compliance 0.5.0 · protocol 2025-03-26 · 23 tools
10 d ago	mcp initialize	ok	200	151 ms	server vitna-compliance 0.5.0 · protocol 2025-03-26 · 23 tools
10 d ago	mcp initialize	ok	200	199 ms	server vitna-compliance 0.5.0 · protocol 2025-03-26 · 23 tools
11 d ago	mcp initialize	ok	200	163 ms	server vitna-compliance 0.5.0 · protocol 2025-03-26 · 23 tools

Tools observed via MCP handshake

vitna_help — What is VITNA and how do I use it to keep myself in check? Call this FIRST after connecting to learn the safety and oversight checks available: how to check ris
vitna_claim — Ask whether this VITNA account has been claimed by a real person yet, and get the link that claims it. Call this when the user asks about their VITNA account, w
consent_check — Before you process someone's personal data, ask VITNA whether an active consent actually permits it for this purpose. Give the data principal + purpose (and opt
breach_classify — After a security incident, check whether it is legally reportable before you decide how to respond. Give the incident facts (affected count, data categories, se
ai_act_classify — Before you build or ship an AI feature, check where it lands under the EU AI Act (Regulation 2024/1689). Describe the use case (with biometric / remote-identifi
dpia_threshold_check — Before you start a new processing activity, check whether the law requires a DPIA first (GDPR Art 35 / DPDP §10 / LGPD Art 38). Give the purpose + data categori
us_sectoral_check — Before you process personal data under US law, find out which US federal sectoral regimes bind you (HIPAA, GLBA, COPPA, FERPA, FCRA, SOX) for a given processing
india_sectoral_check — Before you process personal data under Indian law, find out which sectoral regulators actually bind your specific activity (RBI / SEBI / IRDAI / TRAI / DoT / PF
india_cross_border_status — Before you transfer personal data out of India, check the destination country's DPDP §16 status (permitted / restricted / sectoral_restricted) plus any RBI / SE
japan_cross_border_status — Before you transfer personal data out of Japan, check the destination country's APPI Art 28 status (adequacy / standard basis / high scrutiny). Pass the ISO-316
us_state_breach_deadline — Quick reference lookup of a single US state's breach-notification window, AG recipient and resident threshold (e.g. 'CA' gives 500 residents, CA AG, without unr
aadhaar_mask — Mask + Verhoeff-validate an Aadhaar number. Returns masked form, validity, and an owner-scoped reference token. No persistence of the raw value. Stateless valid
pan_classify — Classify a PAN entity type from the 4th character (P=Person, C=Company, H=HUF, F=Firm, ...). Stateless validator: records no decision and leaves no dashboard ti
gstin_validate — Validate a GSTIN format + mod-36 check digit; returns state code lookup. Stateless validator: records no decision and leaves no dashboard timeline trace.
cpf_validate — Validate a Brazilian CPF (mod-11 check digits, rejects all-same). Stateless validator: records no decision and leaves no dashboard timeline trace.
sin_validate — Validate a Canadian SIN (Luhn checksum); returns series region + masked form. Stateless validator: records no decision and leaves no dashboard timeline trace.
iban_validate — Validate an IBAN format + ISO 7064 mod-97 check digit; supports 71 countries. Stateless validator: records no decision and leaves no dashboard timeline trace.
pii_test — Dry-run VITNA's PII / threat detection on a sample event before you send real data, to preview what would be tagged, how it would be redacted, and whether sever
privacy_notice_get — Generate the operator's jurisdiction-templated privacy notice. Returns markdown or JSON. Stateless generator: records no decision and leaves no dashboard timeli
sub_processors_register — Return the public sub-processor register (Supabase, Vercel, Resend, etc.). Stateless lookup: records no decision and leaves no dashboard timeline trace.
global_compliance_map — Master catalogue of every privacy/security/sectoral regime VITNA has fabric for (28 entries covering 24 named statutes). Stateless lookup: records no decision a
india_regulators_directory — Static reference directory of Indian data and sector regulators (DPB, RBI, SEBI, IRDAI, TRAI, DoT, PFRDA, MeitY, MCA), optionally filtered by sector: a lookup o
vitna_preflight — SAFETY / OVERSIGHT CHECK before a dangerous or destructive action (shell command, file deletion, DB statement, network call). Call this to have VITNA check the

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

npm registry@costrinity/vitna-compliance-mcp

first seen 1 mo ago · fetched 19 h agoopen ↗

Official MCP Registryxyz.costrinity/vitna-compliance-preflight

first seen 1 mo ago · fetched 28 h agoopen ↗

Field history (12 recent events)

28 h ago · declared · description → "Wraps stdio MCP servers. Risky calls wait for a person; no answer, no run. Signed records."
28 h ago · declared · version → "0.5.4"
28 h ago · declared · summary → "Wraps stdio MCP servers. Risky calls wait for a person; no answer, no run. Signed records."
28 h ago · declared · name → "VITNA – Containment for rogue AI agents"
3 d ago · observed · packageFacts → {"name":"@costrinity/vitna-compliance-mcp","registry":"npm","publishedAt":"2026-10-07T04:33:03.376Z","latestVersion":"0.
4 d ago · observed · packageFacts → {"name":"@costrinity/vitna-compliance-mcp","registry":"npm","publishedAt":"2026-10-05T20:08:59.814Z","latestVersion":"0.
4 d ago · declared · version → "0.5.1"
5 d ago · observed · packageFacts → {"name":"@costrinity/vitna-compliance-mcp","registry":"npm","publishedAt":"2026-10-04T05:23:56.918Z","latestVersion":"0.
6 d ago · observed · packageFacts → {"name":"@costrinity/vitna-compliance-mcp","registry":"npm","publishedAt":"2026-09-26T20:00:51.389Z","latestVersion":"0.
12 d ago · declared · description → "Pre-action compliance for AI agents: allow, block or hold. 24 statutes, 13 jurisdictions."
12 d ago · declared · summary → "Pre-action compliance for AI agents: allow, block or hold. 24 statutes, 13 jurisdictions."
12 d ago · declared · version → "0.5.0"

VITNA – Containment for rogue AI agents

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from