@costrinity/vitna-compliance-mcp
OfficialRelated Servers
Alternatives to @costrinity/vitna-compliance-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA pre-action authorization server for AI agents that classifies tool calls into 14 intent categories, scores risk 0-100, and produces deterministic allow/deny/ask decisions with full audit trail.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for AI agent compliance that screens actions before execution and records decisions in an immutable, SIEM-ready audit trail.124 npm-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to screen proposed actions, enforce deterministic policies and limits, and produce tamper-proof signed audit receipts before any external side effect is executed.3 npmMIT
- AlicenseAqualityDmaintenanceCompliance and guardrails infrastructure for AI agents, enabling safe operations within regulatory boundaries like GDPR and EU AI Act.6MIT
- AlicenseBqualityDmaintenancePre-execution governance for AI agents. 45 MCP tools for hold queues, audit trails, risk scoring, and policy enforcement. Validates agent actions before they execute.4554 npm1MIT

@vorionsys/mcp-serverofficial
AlicenseAqualityBmaintenanceMCP server for AI-agent governance using trust scoring, behavioral signals, and pre-flight action checks.1017 npm1Apache 2.0
TDQS
Scored across 23 tools
Each tool has a distinct purpose, and descriptions explicitly clarify overlaps, such as breach_classify vs us_state_breach_deadline and india_sectoral_check vs india_regulators_directory. Validators target different identifiers and checks target different compliance regimes, so an agent can reliably choose the right tool.
All names use snake_case and most follow a resource_action/status pattern (consent_check, gstin_validate, ai_act_classify, india_cross_border_status). Minor deviations exist, including vitna_-prefixed tools and noun-only lookups like global_compliance_map and us_state_breach_deadline, but the set remains readable.
23 tools is on the heavy side for a single MCP server, sitting in the borderline 16-25 range. The compliance domain is broad, but several narrow validators and lookups could potentially be consolidated, making the surface feel somewhat sprawling.
The server covers many advisory checks (consent, breach, DPIA, AI Act, cross-border, sectoral, ID validators), but lacks operational lifecycle tools such as consent create/update/revoke, DSAR handling, incident notification generation, and ROPA/audit retrieval. The surface is broad but incomplete for full compliance management.