VITNA – Containment for rogue AI agents is a remote MCP server that gives an AI agent 23 tools, among them aadhaar_mask, ai_act_classify, breach_classify. It answers at https://vitna.costrinity.xyz/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Guard wraps stdio MCP servers: risky calls wait for a person; no answer, no run. Remote: cooperative
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 validator: records no decision and leaves no dashboard timeline trace. Inputs: aadhaar |
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-identification / automated-decision / social-scoring / GPAI flags) and VITNA returns the Inputs: use_case, data_categories, sectors, automated_decisions, biometric, remote_identification |
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, sensitivity, recovery state) and VITNA returns reportability + reasoning + the not Inputs: affected_count, data_categories, processing_purpose, sensitivity, recovery_state, jurisdiction |
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 optional category); returns { allowed, reason, matching_consent_id, principal_id }, Inputs: principal_id, principal_ref, purpose, category |
cpf_validate | Validate a Brazilian CPF (mod-11 check digits, rejects all-same). Stateless validator: records no decision and leaves no dashboard timeline trace. Inputs: cpf |
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 categories (and scale / systematic-monitoring / automated-decision / cross-border / vuln Inputs: processing_purpose, data_categories, scale, automated_decision, systematic_monitoring, cross_border |
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 and leaves no dashboard timeline trace. |
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. Inputs: gstin |
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. Inputs: iban |
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 / SEBI / IRDAI caveats. Pass the ISO-3166 alpha-2 country code (e.g. US). Stateless Inputs: country |
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 of who exists and what they cover. To instead work out which of them apply to a s Inputs: sector |
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 / PFRDA) from its processing profile, so you know whose rules apply before you act. Inputs: processing_purpose, data_categories, counterparty_types, sector_hint |
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-3166 alpha-2 country code. Stateless lookup: records no decision and leaves no dash Inputs: country |
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 timeline trace. Inputs: pan |
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 severity would escalate. Nothing is persisted and nothing is filtered: a safe rehears Inputs: sample_event, jurisdiction |
privacy_notice_get | Generate the operator's jurisdiction-templated privacy notice. Returns markdown or JSON. Stateless generator: records no decision and leaves no dashboard timeline trace. Inputs: format |
sin_validate | Validate a Canadian SIN (Luhn checksum); returns series region + masked form. Stateless validator: records no decision and leaves no dashboard timeline trace. Inputs: sin |
sub_processors_register | Return the public sub-processor register (Supabase, Vercel, Resend, etc.). Stateless lookup: records no decision and leaves no dashboard timeline trace. |
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 profile, so you can factor them in before you act. US-scoped; for Indian sector Inputs: processing_purpose, data_categories, counterparty_types, ai_decisions, has_revenue_threshold |
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 unreasonable delay). This is a static table, not an incident ruling. When you have Inputs: state |
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, when you are told evidence is not being kept, or any time you want to hand the us |
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 risky actions BEFORE running them, what a deny / hold decision means, trial vs clai |
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 action BEFORE you run it: it flags dangerous shell / SQL / secret-exfil / prompt Inputs: action, payload, action_type |
Every block below points at https://vitna.costrinity.xyz/api/mcp. Pick your client and copy.
claude mcp add --transport http vitna-containment-for-rogue-ai-a https://vitna.costrinity.xyz/api/mcp
{
"mcpServers": {
"vitna-containment-for-rogue-ai-a": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://vitna.costrinity.xyz/api/mcp"]
}
}
}{
"mcpServers": {
"vitna-containment-for-rogue-ai-a": {
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}{
"servers": {
"vitna-containment-for-rogue-ai-a": {
"type": "http",
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}{
"context_servers": {
"vitna-containment-for-rogue-ai-a": {
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}{
"mcpServers": {
"vitna-containment-for-rogue-ai-a": {
"serverUrl": "https://vitna.costrinity.xyz/api/mcp"
}
}
}{
"mcpServers": {
"vitna-containment-for-rogue-ai-a": {
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}name: VITNA – Containment for rogue AI agents
version: 0.0.1
schema: v1
mcpServers:
- name: VITNA – Containment for rogue AI agents
type: streamable-http
url: https://vitna.costrinity.xyz/api/mcp{
"mcpServers": {
"vitna-containment-for-rogue-ai-a": {
"httpUrl": "https://vitna.costrinity.xyz/api/mcp"
}
}
}{
"mcpServers": {
"vitna-containment-for-rogue-ai-a": {
"type": "http",
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}{
"mcpServers": {
"vitna-containment-for-rogue-ai-a": {
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fvitna.costrinity.xyz%2Fapi%2Fmcp&type=streamable_http&id=vitna-containment-for-rogue-ai-a&name=VITNA%20%E2%80%93%20Containment%20for%20rogue%20AI%20agents
It answered our last check on 24 October 2026 in 803 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by costrinity.xyz and served from vitna.costrinity.xyz, the vendor's own domain: https://vitna.costrinity.xyz/api/mcp.
23, as returned by the server's own tools/list on 23 September 2026: aadhaar_mask, ai_act_classify, breach_classify, consent_check, cpf_validate, dpia_threshold_check, global_compliance_map, gstin_validate, and 15 more.
It answered our last check on 24 October 2026 in 803 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vitna.costrinity.xyz/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: xyz.costrinity. Endpoint host: vitna.costrinity.xyz. ARD identifier: urn:air:xyz.costrinity:mcp:vitna-compliance-preflight.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.