INDIVIDUAL MCP TOOL

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

costrinity.xyznone authenticationAvailability not checked

LIVE ENDPOINT

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

No auth detected

Connect to this endpoint to inspect the live schema for japan_cross_border_status and invoke it with your own arguments.

{}

Potential side effects detected · medium confidence · heuristic, not a guarantee.

CONNECT WITH APPROVAL

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.

vitna_help — What is VITNA and how do I use it to keep myself in check?
vitna_claim — Ask whether this VITNA account has been claimed by a real person yet, and get the link that claims it.
consent_check — Before you process someone's personal data, ask VITNA whether an active consent actually permits it for this purpose.
breach_classify — After a security incident, check whether it is legally reportable before you decide how to respond.
ai_act_classify — Before you build or ship an AI feature, check where it lands under the EU AI Act (Regulation 2024/1689).
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).
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.
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.