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
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 15/100 | 热度 0 · 新鲜度 7 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-10-12 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 VITNA – Containment for rogue AI agents。按照 https://mcp.popnx.com/i/xyz-costrinity-vitna-compliance-preflight.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(vitna.costrinity.xyz) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
VITNA – Containment for rogue AI agentshttps://vitna.costrinity.xyz/api/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsVITNA – Containment for rogue AI agents
用 VITNA – Containment for rogue AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 VITNA – Containment for rogue AI agents,或回答中出现 VITNA – Containment for rogue AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
VITNA – Containment for rogue AI agentshttps://vitna.costrinity.xyz/api/mcp开启新聊天,输入前先从插件列表中选择 VITNA – Containment for rogue AI agents
用 VITNA – Containment for rogue AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 VITNA – Containment for rogue AI agents,或回答中出现 VITNA – Containment for rogue AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user vitna-compliance-preflight https://vitna.costrinity.xyz/api/mcp应能看到 VITNA – Containment for rogue AI agents 在列表中并显示已连接
用 VITNA – Containment for rogue AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 VITNA – Containment for rogue AI agents,或回答中出现 VITNA – Containment for rogue AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 VITNA – Containment for rogue AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 VITNA – Containment for rogue AI agents,或回答中出现 VITNA – Containment for rogue AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 VITNA – Containment for rogue AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 VITNA – Containment for rogue AI agents,或回答中出现 VITNA – Containment for rogue AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://vitna.costrinity.xyz/api/mcpJSON 设置在下方“开发者专用”中
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 机密 envVITNA_EMAIL envVITNA_BASE_URL envVITNA_OPEN_CLAIM env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
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
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 costrinity.xyz 验证(注册中心会核实域名所有权)
代码最后更新于35天前
使用 MIT
在 672 毫秒内响应(HTTP 200)
无需登录
已读取 23 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 @costrinity/vitna-compliance-mcp@0.5.6 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/xyz-costrinity-vitna-compliance-preflight)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于35天前,最新版本(0.5.6)于38天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
| 本项 VITNA – Containment for rogue AI agents | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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