Pre-action allow/deny for AI agents. 24 statutes, 13 jurisdictions: EU AI Act, GDPR, DPDP.
MCPpedia last refreshed this data
xyz.costrinity/vitna-compliance-preflight is an MCP server that pre-action allow/deny for AI agents. 24 statutes, 13 jurisdictions: EU AI Act, GDPR, DPDP. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 59/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vitna-compliance": {
"url": "https://vitna.costrinity.xyz/api/mcp",
"type": "streamable-http",
"headers": {
"Authorization": "Bearer vitna_YOUR_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Pre-action compliance for AI agents: allow, block or hold — before your agent acts.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@costrinity/vitna-compliance-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @costrinity/vitna-compliance-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / legal
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
An autonomous agent that conducts deep research on any data using any LLM providers
The official MCP server implementation for the Perplexity API Platform
1000+ scientific tools for AI scientists: life science, reserach, literature, and more.
MCP Security Weekly
Get CVE alerts and security updates for xyz.costrinity/vitna-compliance-preflight and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Renamed from VIGIL. This package was formerly published as
@costrinity/vigil-compliance-mcpand this repo was formerlyCOSTRINITY/vigil-compliance-mcp. The old package name does not exist on npm — anything still pointing at it will fail to install. Directory listings that show the VIGIL name are stale snapshots of this repo.Current package:
@costrinity/vitna-compliance-mcpRegistry entry:xyz.costrinity/vitna-compliance-preflightSite: https://vitna.costrinity.xyz
Pre-action compliance for AI agents: allow, block or hold — before your agent acts.
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.
| 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 |
| 22 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 is a cooperative guardrail with heuristic detection, and those limits are documented publicly. Its purpose is not prevention. It is independently verifiable proof that an AI agent's actions were checked and allowed.
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? | 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 | 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 also produces an Ed25519-signed evidence record that anyone can verify offline — no account, and no trust in VITNA's servers required. 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 in