Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
Guard wraps stdio MCP servers: risky calls wait for a person; no answer, no run. Remote: cooperative
This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order
| 1. In Claude’s connector directory | No | |
|---|---|---|
| 2. Tried by our team | No | |
| 3. Works for Thai users | No | |
| 4. Usage without stars | 15/100 | Popularity 0 · Freshness 7 · Still answering 8 · Likes from users +0 |
| 5. Listed on | 2026-10-12 |
Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.
Quality: Passed 5/5 basic checks (shown, not used for ordering)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install VITNA – Containment for rogue AI agents. Follow https://mcp.popnx.com/i/xyz-costrinity-vitna-compliance-preflight.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (vitna.costrinity.xyz) · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
VITNA – Containment for rogue AI agentshttps://vitna.costrinity.xyz/api/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsVITNA – Containment for rogue AI agents
Use VITNA – Containment for rogue AI agents and tell me what you can do for me, then show me one thing✓ If Claude says it is using VITNA – Containment for rogue AI agents or shows a VITNA – Containment for rogue AI agents tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
VITNA – Containment for rogue AI agentshttps://vitna.costrinity.xyz/api/mcpStart a new chat and pick VITNA – Containment for rogue AI agents from your plugins before typing
Use VITNA – Containment for rogue AI agents and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using VITNA – Containment for rogue AI agents or shows a VITNA – Containment for rogue AI agents tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user vitna-compliance-preflight https://vitna.costrinity.xyz/api/mcpYou should see VITNA – Containment for rogue AI agents listed as connected
Use VITNA – Containment for rogue AI agents and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using VITNA – Containment for rogue AI agents or shows a VITNA – Containment for rogue AI agents tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use VITNA – Containment for rogue AI agents and tell me what you can do for me, then show me one thing✓ If Cursor says it is using VITNA – Containment for rogue AI agents or shows a VITNA – Containment for rogue AI agents tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use VITNA – Containment for rogue AI agents and tell me what you can do for me, then show me one thing✓ If VS Code says it is using VITNA – Containment for rogue AI agents or shows a VITNA – Containment for rogue AI agents tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://vitna.costrinity.xyz/api/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user vitna-compliance-preflight https://vitna.costrinity.xyz/api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vitna-compliance-preflight": {
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"vitna-compliance-preflight": {
"type": "http",
"url": "https://vitna.costrinity.xyz/api/mcp"
}
}
}Claude Code
claude mcp add --scope user vitna-compliance-preflight -- npx -y @costrinity/vitna-compliance-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"vitna-compliance-preflight": {
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vitna-compliance-preflight": {
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"vitna-compliance-preflight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
]
}
}
}VITNA_OWNER_ID envVITNA_API_KEY secret envVITNA_EMAIL envVITNA_BASE_URL envVITNA_OPEN_CLAIM envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @costrinity/vitna-compliance-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Tool names and descriptions exactly as the server reported them on Nov 18, 2026. The maker wrote them, not us; we show them as plain text.
vitna_helpWhat 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 a
vitna_claimAsk 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 li
consent_checkBefore 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 yoursel
breach_classifyAfter 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, acro
ai_act_classifyBefore 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 / lim
dpia_threshold_checkBefore 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_req
us_sectoral_checkBefore 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.
india_sectoral_checkBefore 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 wha
india_cross_border_statusBefore 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 n
japan_cross_border_statusBefore 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.
us_state_breach_deadlineQuick 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 rep
aadhaar_maskMask + 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.
pan_classifyClassify 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.
gstin_validateValidate a GSTIN format + mod-36 check digit; returns state code lookup. Stateless validator: records no decision and leaves no dashboard timeline trace.
cpf_validateValidate a Brazilian CPF (mod-11 check digits, rejects all-same). Stateless validator: records no decision and leaves no dashboard timeline trace.
sin_validateValidate a Canadian SIN (Luhn checksum); returns series region + masked form. Stateless validator: records no decision and leaves no dashboard timeline trace.
iban_validateValidate an IBAN format + ISO 7064 mod-97 check digit; supports 71 countries. Stateless validator: records no decision and leaves no dashboard timeline trace.
pii_testDry-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
privacy_notice_getGenerate 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 dashbo
sub_processors_registerReturn the public sub-processor register (Supabase, Vercel, Resend, etc.). Stateless lookup: records no decision and leaves no dashboard timeline trace.
global_compliance_mapMaster 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.
india_regulators_directoryStatic 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_s
vitna_preflightSAFETY / 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
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified against the domain costrinity.xyz (the registry checks domain ownership)
Code last changed 35 days ago
Uses MIT
Responded in 672 ms (HTTP 200)
No sign-in needed
Read 23 tool descriptions and found no hidden instructions to the AI
No entries on OSV.dev for @costrinity/vitna-compliance-mcp@0.5.6
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/xyz-costrinity-vitna-compliance-preflight)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed 35 days ago, and the latest version (0.5.6) reached the registry 38 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Search French-language and European case law and French legal texts (codes, statutes, treaties).
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.
| This one VITNA – Containment for rogue AI agents | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A containment layer for AI agents that go rogue.
Agents go rogue through their tools. VITNA sits on the tools you put behind it. Calls to the tools you mark as risky wait for a person. No answer, no run. No API key can decide a hold, including the agent's own. Claimed accounts get signed records you can check offline.
[Try the demo](https://vitna.costrinity.xyz/demo): a labelled simulation in your browser. A scripted agent on pretend files reaches for risky tools, and you decide its held calls. No install, nothing stored.
npx -y @costrinity/vitna-compliance-mcp guard -- <your stdio MCP server command>
To see a hold, give the guard a policy file that lists the tools to hold. The reference filesystem server has no delete tool: it destroys a file by overwriting or moving it, so this policy.json holds those calls and allows the rest:
{ "allowed_actions": ["*"], "hold_actions": ["write_file", "edit_file", "move_file"] }
VITNA_GUARD_POLICY=/path/to/policy.json npx -y @costrinity/vitna-compliance-mcp guard -- npx -y @modelcontextprotocol/server-filesystem /path/to/test-folder
In an MCP client config, put VITNA_GUARD_POLICY under env (see Guard mode).
Every tools/call is checked by VITNA before it reaches the server. Anything not allowed is refused with a tool error that says why. With no credentials you get a trial key: a risky call is held, and with nobody able to approve it yet, it's blocked when the window ends. To approve or deny holds and keep signed records, claim the account with GitHub or a passkey, then decide holds in the Aquarium on your dashboard. The claim link is printed in your MCP server log and never sent to the agent; VITNA_OPEN_CLAIM=1 opens it in your browser.
Try it on a test agent first.
VITNA sees only the servers it wraps. A built-in shell or an unwrapped server is outside it, so turn those off if you want every action to go through the guard. The session record lists what you declared as unwrapped. The remote endpoint offers the same checks as tools an agent calls itself; that's cooperative, not containment. Detection is heuristic pattern matching, not a sandbox.
What it doesn't do · Guard mode · Verify a record
The guard wraps stdio MCP servers, so it can sit in front of a client or SDK that launches stdio MCP servers. A setup is listed as tested only after we have run it with the guard.
The config for each is on Connect your agent; Compatibility says which are tested.
Not supported:
This package was formerly published as @costrinity/vigil-compliance-mcp and this repo was formerly COSTRINITY/vigil-compliance-mcp. The old package is still on npm at 0.2.4, deprecated with the message "Renamed: use @costrinity/vitna-compliance-mcp". It gets no updates and has no guard mode, so anything still pointing at it installs that old version. Directory listings that show the VIGIL name are stale snapshots of this repo.
Current package: `@costrinity/vitna-compliance-mcp` Registry entry: `xyz.costrinity/vitna-compliance-preflight` Site: https://vitna.costrinity.xyz
The same package carries VITNA's compliance checks: 23 MCP tools across 24 named statutes in 13 jurisdictions, for an agent to call itself before it acts. Decision support, not legal advice; scorecards are not certifications.
Most compliance servers answer questions *about* regulations. This one answers one question *about the action your agent is holding right now*: may it run? Your agent calls a check, gets allowed / blocked / flagged back synchronously, and decides. VITNA evaluates and records; your system enforces.
One package to install. This is the server your agent calls before it acts.
| Package | What it does | When you want it | Install |
|---|---|---|---|
| `@costrinity/vitna-compliance-mcp` (this one) | Your agent asks before it acts. Returns allow / block / flag on a proposed action, and records a signed evidence record of the decision. | You want a guardrail your agent calls, and provable receipts that it did. | npx @costrinity/vitna-compliance-mcp — no credentials needed to start |
A passive observer that records existing MCP traffic without deciding anything is built in this repo but is not published to npm, so it is not documented here yet. Nothing above depends on it.
| 24 named statutes | across 13 jurisdictions |
| EU AI Act (Reg 2024/1689) | risk-tier classification before you build or ship |
| GDPR + UK GDPR | DPIA thresholds, breach reportability, ROPA |
| DPDP (India, 2023) | §16 cross-border status, §8 breach path |
| LGPD · PDPA-SG · APPI · PIPEDA + Law 25 · PIPL · PIPA-KR · NDPA · APP-AU · CPRA | jurisdiction packs |
| HIPAA · GLBA · COPPA · FERPA · FCRA · SOX | US federal sectoral applicability |
| RBI · SEBI · IRDAI · TRAI/DoT · PFRDA | Indian sectoral regulators |
| 16 US state privacy laws | plus breach deadlines for 21 states |
| 23 MCP tools | 6 identifier validators, 15 stateless helpers |
Readiness scorecards (pre-audit, not certifications) additionally cover NIST Privacy Framework, SOC 2, ISO/IEC 27001 and PCI DSS v4.0.
Every count above is derived from the code and enforced by a build gate — if an implementation is removed, the build fails before the number can go stale. See "Honest limits" below for what these numbers do *not* mean.
VITNA's detection is heuristic, and those limits are documented publicly. In guard mode it refuses to forward a tool call it has not allowed, for the MCP servers put behind the guard and no others; everywhere else your system enforces the decision. Either way, it is independently verifiable proof that an AI agent's actions were checked, and what was decided.
Two questions people usually have to answer *before* they need any of this. Both run entirely in the browser, take a few questions, and store nothing.
| [Does the 2 December 2026 deadline apply to you?](https://vitna.costrinity.xyz/ai-act-december-2026) | Article 50(2) machine-readable marking for generative systems placed on the EU market before 2 August 2026, plus the two prohibited practices added by the Digital Omnibus. Works out which of the two dates you are actually on. |
| [Article 50 transparency self-check](https://vitna.costrinity.xyz/article-50) | Which Article 50 disclosure duties reach you as provider or deployer. |
Both are scoping tools, not legal advice, and neither issues a score or a pass/fail. They cite the article and the Official Journal text behind every date they state.
Every decision on a claimed account also produces an Ed25519-signed evidence record that anyone can verify offline, with no account of their own and no trust in VITNA's servers. The public key is published, the verifier is open source, and the three commands below prove it in about a minute.
One minute, no account, no trust in VITNA's servers required. Download the open-source verifier and a real signed sample bundle, then check the signature offline with Node 18+:
curl -sO https://raw.githubusercontent.com/COSTRINITY/vitna-compliance-mcp/main/verify-evidence.mjs
curl -sO https://vitna.costrinity.xyz/sample-evidence.json node verify-evidence.mjs sample-evidence.json
The verifier checks the Ed25519 signature over the whole package, then recomputes the sha256 of each individual decision record and confirms it matches the hash committed inside the signed package, printing PASS or FAIL per record, then an overall verdict.
Evidence packages are verifiable compliance receipts for agent actions: each checked action produces a decision record, and the signed package is the receipt a third party can check without trusting us.
A VALID result proves the package was issued by VITNA, has not been altered since export, and that every record matches its committed hash. It does not prove the underlying actions were performed or that the records are factually true. Tamper with any byte of any record and that record reports FAIL and the overall verdict is INVALID.
Bundles from VITNA Desktop are signed differently. VITNA Desktop signs on your own machine, with a key it generated there, not with VITNA's key. The signed package says so (issuer: "vitna-desktop-local", signer_key_id, signer_public_key), and the verifier reports such a bundle as "signed by a local VITNA Desktop key, not by VITNA". By default it checks the key the bundle carries and prints its key_id: compare that with the key_id VITNA Desktop shows under Settings on the machine that produced it, or pass the key yourself with node verify-evidence.mjs --pubkey bundle.json. Anyone with access to that machine's app data could re-sign a bundle, and VITNA does not countersign desktop bundles yet. A key carried inside a bundle is used only for that issuer: every other bundle is checked against VITNA's published key, so a self-signed bundle canno