Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/COSTRINITY/vitna-compliance-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/costrinity/vitna-compliance-mcp/vitna-compliance-preflight)<a href="https://agentmods.dev/mcp/costrinity/vitna-compliance-mcp/vitna-compliance-preflight"><img src="https://agentmods.dev/badge/mcp/costrinity/vitna-compliance-mcp/vitna-compliance-preflight/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/costrinity/vitna-compliance-mcp/vitna-compliance-preflight"><img src="https://agentmods.dev/badge/mcp/costrinity/vitna-compliance-mcp/vitna-compliance-preflight.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vitna-compliance-preflight scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"vitna-compliance-preflight": {
"command": "npx",
"args": [
"-y",
"@costrinity/vitna-compliance-mcp"
],
"env": {
"VITNA_OWNER_ID": "",
"VITNA_API_KEY": "",
"VITNA_EMAIL": "",
"VITNA_BASE_URL": "https://vitna.costrinity.xyz"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 15 lines scan A af1adbf3cb0c
vitna-compliance-preflight is an MCP server published in the GitHub repository COSTRINITY/vitna-compliance-mcp (0 stars, last pushed 22d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-eu-ai-act
EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected. Remote server at mcp.arkforge.tech.
kakunin
X.509 identity, risk scoring, and audit logging for AI agents. MiCA + EU AI Act compliant. Runs locally from the @kakunin/mcp npm package. Needs 2 environment variables to run.
whitepact
ResponsibleAI — Enterprise AI Governance Platform: trust scoring, bias detection, hallucination detection, guardrails, compliance (NIST AI RMF / EU AI Act / ISO 42001), cost intelligence, drift monitoring. Runs locally from the rai-governance-platform Python package. Needs 1 environment variable to run.
ai-incident-law
Public-record corpus of AI litigation, regulation, and enforcement, anchored to EveryAILaw. Runs locally from the ai-incident-law npm package.
ai-bom-mcp
AI Bill of Materials (AI-BOM) generator + auditor MCP — CycloneDX ML-BOM, SPDX 3.0 AI profile, EU AI Act Annex IV mapping, NIST AI RMF alignment, US EO 14028 federal procurement. By MEOK AI Labs. Runs locally from the ai-bom-mcp Python package.
vaara
Accountable Autonomy for AI agents under the EU AI Act: policy-gated tool calls, hash-chained tamper-evident audit trails with external time anchoring, and independently verifiable attestation plus execution receipts per MCP tool call. Runs locally from the vaara Python package.