Is the Costrinity Vitna Compliance Preflight MCP server down?

mcp-registry/xyz.costrinity/vitna-compliance-preflight · v0.5.6

Also listed as glama/costrinity/-costrinity/vitna-compliance-mcp

healthy
Last checked 2026-10-26 21:27 UTC · handshake 803ms

As of 2026-10-26 21:27 UTC, the Costrinity Vitna Compliance Preflight MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
100%
checks observed
4,511
outages (90d)
2
tools
23

Pre-action compliance for AI agents: allow, block or hold. 24 statutes, 13 jurisdictions.

Point your MCP client at this streamable-http endpoint: https://vitna.costrinity.xyz/api/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 3 warning(s) across 23 tool(s); ~3,521 tokens of tool definitions.
Scores higher than 5% of 15,763 MCP servers Glimind has audited.
Its tool list costs an agent ~3,521 tokens per session — more than 55% of servers.
70 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions47
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (4)

23 of 23 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: aadhaar_mask, ai_act_classify, breach_classify, consent_check, cpf_validate and 18 more

40 parameter(s) across 14 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: aadhaar_mask, ai_act_classify, breach_classify, cpf_validate, dpia_threshold_check and 9 more

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 11 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 14 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.costrinity%2Fvitna-compliance-preflight/fixes

consent_check 1 change 
{
  "name": "consent_check",
  "description": "Before you process someone's personal data, ask VITNA whether an active consent actually permits it for this purpose. Give the data principal + purpose (and optional category); returns { allowed, reason, matching_consent_id, principal_id }, a determination you must honour yourself since VITNA evaluates and records but does not enforce. Use this for personal-data processing legality; for a dangerous technical action (shell / file / DB / network) use vitna_preflight instead.",
  "inputSchema": {
    "type": "object",
    "required": [
      "purpose"
    ],
    "properties": {
      "purpose": {
        "type": "string",
        "description": "Purpose code (e.g. 'operational_observability')."
      },
      "category": {
        "type": "string",
        "description": "Optional permitted-category check."
      },
      "principal_id": {
        "type": "string",
        "description": "UUID of the data principal (if known)."
      },
      "principal_ref": {
        "type": "string",
        "description": "Operator-side identifier; will be SHA-256-hashed."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
cpf_validate 1 change 
{
  "name": "cpf_validate",
  "description": "Validate a Brazilian CPF (mod-11 check digits, rejects all-same). Stateless validator: records no decision and leaves no dashboard timeline trace.",
  "inputSchema": {
    "type": "object",
    "required": [
      "cpf"
    ],
    "properties": {
      "cpf": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
dpia_threshold_check 1 change 
{
  "name": "dpia_threshold_check",
  "description": "Before you start a new processing activity, check whether the law requires a DPIA first (GDPR Art 35 / DPDP §10 / LGPD Art 38). Give the purpose + data categories (and scale / systematic-monitoring / automated-decision / cross-border / vulnerable-subjects flags); returns dpia_required + the 9-criterion WP29 analysis + jurisdiction guidance, so you know whether to pause and assess before proceeding.",
  "inputSchema": {
    "type": "object",
    "required": [
      "processing_purpose",
      "data_categories"
    ],
    "properties": {
      "scale": {
        "enum": [
          "small",
          "medium",
          "large",
          "mass"
        ],
        "type": "string"
      },
      "cross_border": {
        "type": "boolean"
      },
      "jurisdiction": {
        "type": "string"
      },
      "data_categories": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "automated_decision": {
        "type": "boolean"
      },
      "processing_purpose": {
        "type": "string"
      },
      "vulnerable_subjects": {
        "type": "boolean"
      },
      "systematic_monitoring": {
        "type": "boolean"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.costrinity/vitna-compliance-preflight"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/xyz.costrinity/vitna-compliance-preflight"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.costrinity%2Fvitna-compliance-preflight.svg)](https://glimind.com/server/mcp-registry%2Fxyz.costrinity%2Fvitna-compliance-preflight?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fxyz.costrinity%2Fvitna-compliance-preflight?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.costrinity%2Fvitna-compliance-preflight.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.costrinity%2Fvitna-compliance-preflight.svg
   :target: https://glimind.com/server/mcp-registry%2Fxyz.costrinity%2Fvitna-compliance-preflight?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:09ea0cd1884022d7…, first seen 2026-10-17, included at leaf 15044 of 75,543. Version history · verify what your client received.

Tools (23)

Compare: most reliable data servers · most reliable security servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Costrinity Vitna Compliance Preflight MCP server down right now?

As of 2026-10-26 21:27 UTC, the Costrinity Vitna Compliance Preflight MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 10 minutes.

How many tools does Costrinity Vitna Compliance Preflight MCP server provide?

Costrinity Vitna Compliance Preflight MCP server advertises 23 tools, including aadhaar_mask, ai_act_classify, breach_classify, consent_check, cpf_validate.

How do I install Costrinity Vitna Compliance Preflight MCP server?

Point your MCP client at this streamable-http endpoint: https://vitna.costrinity.xyz/api/mcp

Is the Costrinity Vitna Compliance Preflight MCP server safe to connect to an AI agent?

Glimind scanned all 23 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Costrinity Vitna Compliance Preflight MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve