{"id":"xyz.costrinity/vitna-compliance-preflight","slug":"xyz-costrinity-vitna-compliance-preflight","title":"VITNA – Containment for rogue AI agents","description":"Guard wraps stdio MCP servers: risky calls wait for a person; no answer, no run. Remote: cooperative","version":"0.5.6","publisher":{"kind":"domain","id":"costrinity.xyz","label":"costrinity.xyz","url":"https://costrinity.xyz"},"website":"https://vitna.costrinity.xyz","repository":"https://github.com/COSTRINITY/vitna-compliance-mcp","remotes":[{"type":"streamable-http","url":"https://vitna.costrinity.xyz/api/mcp","headers":[{"description":"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.","isSecret":true,"name":"Authorization"}]}],"packages":[{"registryType":"npm","registryBaseUrl":"https://registry.npmjs.org","identifier":"@costrinity/vitna-compliance-mcp","version":"0.5.6","transport":{"type":"stdio"},"environmentVariables":[{"description":"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.","name":"VITNA_OWNER_ID"},{"description":"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.","isSecret":true,"name":"VITNA_API_KEY"},{"description":"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.","name":"VITNA_EMAIL"},{"description":"VITNA base URL; override only for self-hosted. The old VIGIL_BASE_URL name is still accepted.","default":"https://vitna.costrinity.xyz","name":"VITNA_BASE_URL"},{"description":"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.","name":"VITNA_OPEN_CLAIM"}]}],"published":"2026-10-12","updated":"2026-10-12","status":"online","auth":"","latency_ms":1556,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"vitna_help","title":"","description":"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 risky actions BEFORE running them, what a deny / hold decision means, trial vs claimed mode, and how the user can monitor and audit what you do. Runs entirely locally: no account, no API call, and no dashboard timeline trace.","read_only":false},{"name":"vitna_claim","title":"","description":"Ask whether this VITNA account has been claimed by a real person yet. Call this when the user asks about their VITNA account or when you are told evidence is not being kept. Returns { claimed, claim_url: null, claim_note, what_claiming_gets_you }. You are never given the claim link, and you must not look for it: only a person may claim the account that oversees you. If claimed is false, tell the u","read_only":false},{"name":"consent_check","title":"","description":"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 optional category); returns { allowed, reason, matching_consent_id, principal_id }, a determination you must honour yourself since VITNA evaluates and records but does not enforce. Use this for personal-data processing legality; for a dangerou","read_only":false},{"name":"breach_classify","title":"","description":"After a security incident, check whether it is legally reportable before you decide how to respond. Give the incident facts (affected count, data categories, sensitivity, recovery state) and VITNA returns reportability + reasoning + the notification deadline + who to notify, across DPDP §8, GDPR Art 33, CPRA §1798.82, LGPD Art 48, PDPA §26B, and US-FED sectoral. This makes the full incident decisi","read_only":false},{"name":"ai_act_classify","title":"","description":"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-identification / automated-decision / social-scoring / GPAI flags) and VITNA returns the risk tier (prohibited / high-risk / limited-risk / minimal-risk), GPAI obligations, and the per-tier obligations you would have to meet. A classification for y","read_only":false},{"name":"dpia_threshold_check","title":"","description":"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 categories (and scale / systematic-monitoring / automated-decision / cross-border / vulnerable-subjects flags); returns dpia_required + the 9-criterion WP29 analysis + jurisdiction guidance, so you know whether to pause and assess before proceeding","read_only":false},{"name":"us_sectoral_check","title":"","description":"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 profile, so you can factor them in before you act. US-scoped; for Indian sectoral regulators use india_sectoral_check.","read_only":false},{"name":"india_sectoral_check","title":"","description":"Before you process personal data under Indian law, find out which sectoral regulators actually bind your specific activity (RBI / SEBI / IRDAI / TRAI / DoT / PFRDA) from its processing profile, so you know whose rules apply before you act. This analyses your processing to say what applies; for a plain directory of every Indian regulator regardless of your activity, use india_regulators_directory.","read_only":false},{"name":"india_cross_border_status","title":"","description":"Before you transfer personal data out of India, check the destination country's DPDP §16 status (permitted / restricted / sectoral_restricted) plus any RBI / SEBI / IRDAI caveats. Pass the ISO-3166 alpha-2 country code (e.g. US). Stateless lookup: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"japan_cross_border_status","title":"","description":"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-3166 alpha-2 country code. Stateless lookup: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"us_state_breach_deadline","title":"","description":"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 unreasonable delay). This is a static table, not an incident ruling. When you have the actual incident facts and need a reportable / not-reportable decision with reasoning, use breach_classify instead. Stateless lookup: records no decision and","read_only":false},{"name":"aadhaar_mask","title":"","description":"Mask + Verhoeff-validate an Aadhaar number. Returns masked form, validity, and an owner-scoped reference token. No persistence of the raw value. Stateless validator: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"pan_classify","title":"","description":"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 timeline trace.","read_only":false},{"name":"gstin_validate","title":"","description":"Validate a GSTIN format + mod-36 check digit; returns state code lookup. Stateless validator: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"cpf_validate","title":"","description":"Validate a Brazilian CPF (mod-11 check digits, rejects all-same). Stateless validator: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"sin_validate","title":"","description":"Validate a Canadian SIN (Luhn checksum); returns series region + masked form. Stateless validator: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"iban_validate","title":"","description":"Validate an IBAN format + ISO 7064 mod-97 check digit; supports 71 countries. Stateless validator: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"pii_test","title":"","description":"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 severity would escalate. Nothing is persisted and nothing is filtered: a safe rehearsal you act on, not an enforced gate — it records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"privacy_notice_get","title":"","description":"Generate the operator's jurisdiction-templated privacy notice. Returns markdown or JSON. Called with an API key, the operator's name and contact details appear as placeholders; the signed-in owner gets the real values. Stateless generator: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"sub_processors_register","title":"","description":"Return the public sub-processor register (Supabase, Vercel, Resend, etc.). Stateless lookup: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"global_compliance_map","title":"","description":"Master catalogue of every privacy/security/sectoral regime VITNA has fabric for (28 entries covering 24 named statutes). Stateless lookup: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"india_regulators_directory","title":"","description":"Static reference directory of Indian data and sector regulators (DPB, RBI, SEBI, IRDAI, TRAI, DoT, PFRDA, MeitY, MCA), optionally filtered by sector: a lookup of who exists and what they cover. To instead work out which of them apply to a specific processing activity, use india_sectoral_check. Stateless lookup: records no decision and leaves no dashboard timeline trace.","read_only":false},{"name":"vitna_preflight","title":"","description":"SAFETY / OVERSIGHT CHECK before a dangerous or destructive action (shell command, file deletion, DB statement, network call). Call this to have VITNA check the action BEFORE you run it: it flags dangerous shell / SQL / secret-exfil / prompt-injection / suspicious-network patterns and returns { decision: allowed|blocked|flagged }. RESPONSE SHAPE DEPENDS ON THE KEY: an unclaimed trial key gets the d","read_only":false}],"server_info":{"name":"vitna-compliance","version":"0.5.7"},"category":"legal","tags":["agents","travel"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-08-11","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/xyz-costrinity-vitna-compliance-preflight/"}