Skip to main content
Glama
COSTRINITY

@costrinity/vitna-compliance-mcp

Official

Related Servers

Alternatives to @costrinity/vitna-compliance-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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
    • F
      license
      Not graded
      quality
      F
      maintenance
      MCP server for AI agent compliance that screens actions before execution and records decisions in an immutable, SIEM-ready audit trail.
      84 npm
      -
    • A
      license
      A
      quality
      A
      maintenance
      Owner-signed authorization before agent actions. Hosted Vizier v0.5.13 MCP: https://vizier.agendamcp.dpdns.org/mcp. ALLOW/BLOCK/REVIEW; anonymous calls never ALLOW. Your integration enforces the decision. SDK v0.5.13: https://www.npmjs.com/package/@agenda-intelligence/vizier-sdk. Grants are signed; legacy receipts are unsigned. Python stdio is a separate catalog.
      3
      7 npm
      MIT

    TDQS

    A4/5.0

    Scored across 23 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive