← Registry

Security & Testing

costrinity.xyz

An MCP server that provides VITNA compliance guidance for consent checks, data breach reporting, and EU AI Act classification.

1 endpoint23 known toolsFirst detected June 6, 2026Last detected September 11, 2026

ENDPOINT 1

https://vitna.costrinity.xyz/api/mcp

No auth detected

MCP server metadata

Name
vitna-compliance
Version
0.3.7
Capabilities
tools

Known tools 23

vitna_help

What is VITNA and how do I use it to keep myself in check?

Inferred read-only
vitna_claim

Ask whether this VITNA account has been claimed by a real person yet, and get the link that claims it.

Inferred read-only
consent_check

Before you process someone's personal data, ask VITNA whether an active consent actually permits it for this purpose.

Inferred read-only
breach_classify

After a security incident, check whether it is legally reportable before you decide how to respond.

Inferred read-only
ai_act_classify

Before you build or ship an AI feature, check where it lands under the EU AI Act (Regulation 2024/1689).

Inferred read-only
dpia_threshold_check

Before you start a new processing activity, check whether the law requires a DPIA first (GDPR Art 35 / DPDP §10 / LGPD Art 38).

Inferred read-only
us_sectoral_check

Before 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.

Inferred read-only
india_sectoral_check

Before 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.

Inferred read-only
india_cross_border_status

Before 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.

Potential side effects
japan_cross_border_status

Before you transfer personal data out of Japan, check the destination country's APPI Art 28 status (adequacy / standard basis / high scrutiny).

Potential side effects
us_state_breach_deadline

Quick reference lookup of a single US state's breach-notification window, AG recipient and resident threshold (e.

Inferred read-only
aadhaar_mask

Mask + Verhoeff-validate an Aadhaar number.

Inferred read-only
pan_classify

Classify a PAN entity type from the 4th character (P=Person, C=Company, H=HUF, F=Firm, .

Inferred read-only
gstin_validate

Validate a GSTIN format + mod-36 check digit; returns state code lookup.

Inferred read-only
cpf_validate

Validate a Brazilian CPF (mod-11 check digits, rejects all-same).

Inferred read-only
sin_validate

Validate a Canadian SIN (Luhn checksum); returns series region + masked form.

Inferred read-only
iban_validate

Validate an IBAN format + ISO 7064 mod-97 check digit; supports 71 countries.

Inferred read-only
pii_test

Dry-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.

Potential side effects
privacy_notice_get

Generate the operator's jurisdiction-templated privacy notice.

Inferred read-only
sub_processors_register

Return the public sub-processor register (Supabase, Vercel, Resend, etc.

Inferred read-only
global_compliance_map

Master catalogue of every privacy/security/sectoral regime VITNA has fabric for (28 entries covering 24 named statutes).

Inferred read-only
india_regulators_directory

Static 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.

Inferred read-only
vitna_preflight

SAFETY / OVERSIGHT CHECK before a dangerous or destructive action (shell command, file deletion, DB statement, network call).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vitna-compliance]
url = "https://vitna.costrinity.xyz/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "vitna-compliance": {
      "type": "http",
      "url": "https://vitna.costrinity.xyz/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: vitna-compliance
Remote MCP URL: https://vitna.costrinity.xyz/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vitna-compliance": {
      "url": "https://vitna.costrinity.xyz/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "vitna-compliance": {
      "type": "http",
      "url": "https://vitna.costrinity.xyz/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "vitna-compliance",
  "transport": "streamable-http",
  "url": "https://vitna.costrinity.xyz/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.