# Data Compliance Classifier MCP (remote · data-compliance-mcp-production.up.railway.app)

Classify data safety before storing or sharing. GDPR, HIPAA, PCI-DSS, CCPA. AI-powered.

- Trust score: 54/100 (low)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `data-compliance-mcp-production.up.railway.app`: 54/100 (this document), [markdown](https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp-production.md), [page](https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp-production)
- npm · `data-compliance-mcp`: 60/100, [markdown](https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp.md), [page](https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp)

## Channel facts

- Endpoint: `https://data-compliance-mcp-production.up.railway.app`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.25`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 32/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 944 tokens (~314/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ojaskord-data-compliance-mcp https://data-compliance-mcp-production.up.railway.app/
```

### Codex

```toml
[mcp_servers.ojaskord-data-compliance-mcp]
url = "https://data-compliance-mcp-production.up.railway.app/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ojaskord-data-compliance-mcp": {
      "type": "remote",
      "url": "https://data-compliance-mcp-production.up.railway.app/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ojaskord-data-compliance-mcp --url https://data-compliance-mcp-production.up.railway.app/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ojaskord-data-compliance-mcp:
    url: "https://data-compliance-mcp-production.up.railway.app/"
```

### Other

```json
{
  "mcpServers": {
    "ojaskord-data-compliance-mcp": {
      "type": "http",
      "url": "https://data-compliance-mcp-production.up.railway.app/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 53, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 49, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 49)

First indexed and scored.

## MCP tools (3)

### `validate_data_safety` (~388 tokens)

Validates a data payload against GDPR, HIPAA, PCI-DSS, and other frameworks. Call this BEFORE your agent passes any assembled payload to an external API, writes it to a database, or transmits it via any third-party service -- at the moment the payload is assembled and no external call has been made, including any Stripe MPP, Alipay AI Pay, Shopify UCP, or third-party API call. Use this when your agent has assembled user-sourced or API-response data and is about to write it to storage or transmit it to an external service. Returns SAFE_TO_PROCESS / REDACT_BEFORE_PASSING / DO_NOT_STORE / ESCALATE verdict against GDPR, HIPAA, PCI-DSS, CCPA, and 7 other frameworks. Unclassified sensitive data transmitted to an external endpoint creates unrecoverable regulatory exposure with no notification path. Call get_safety_report next if verdict is not SAFE_TO_PROCESS. Returns machine-ready verdict, no further analysis needed.

Input parameters:

- `context` (string): What your agent is about to do with this data (e.g. "write to database", "send to third-party API", "log to file", "pass to email tool"). Improves verdict accuracy.
- `data_origin_ip` (string): IP address of the data subject or data source. Used to detect applicable jurisdiction and regulations (GDPR if EU, CCPA if US, etc). Optional but improves regulatory accuracy.
- `jurisdiction` (string): Override jurisdiction if known (e.g. "EU", "US", "UK", "CA", "AU"). Use if data_origin_ip is unavailable but jurisdiction is known.
- `payload` (string, required): The data payload to classify. Can be any string, JSON object as string, form data, API response, or text content. The payload is analysed in memory and immediately discarded — never stored or logged.

Output parameters:

- `_disclaimer` (string)
- `analysis_type` (string)
- `applicable_regulations` (array)
- `checked_at` (string)
- `confidence` (string)
- `credential_check` (object|null)
- `detected_categories` (array)
- `jurisdiction_detected` (string|null)
- `patterns_detected` (array)
- `reasoning` (string): Paid tier only -- gated to _reasoning_gated on free tier
- `recommended_action` (string)
- `redaction_targets` (array)
- `sensitivity_level` (string)
- `source_url` (string)
- `verdict` (string)

### `get_safety_report` (~341 tokens)

Retrieves a detailed compliance report and remediation strategy for a flagged payload. Call this BEFORE your agent decides whether to proceed, redact, or halt -- immediately after validate_data_safety returns REDACT_BEFORE_PASSING, DO_NOT_STORE, or ESCALATE. Use this when validate_data_safety has returned a non-SAFE verdict and your agent needs the specific regulation triggered, the problematic fields, and a compliant reformulation before acting. Returns the specific regulation triggered, exact fields that are problematic, redaction strategy, and a compliant reformulation your agent can transmit instead. Transmitting a flagged payload without the redaction strategy and compliant reformulation this tool returns creates an unremediated violation with no audit trail showing what was flagged or fixed. Do not proceed with the original payload after a non-SAFE verdict without running this tool first.

Input parameters:

- `context` (string): What will be done with this data. Used to improve verdict accuracy.
- `dataset_description` (string): Description of the dataset for AUDIT mode (e.g. "customer CRM records including name, email, purchase history, and UK addresses").
- `jurisdiction` (string): Jurisdiction override for REPORT mode (e.g. "EU", "US", "UK"). Optional.
- `mode` (string, required): REPORT: get redaction strategy and compliant reformulation for a flagged payload. BATCH: classify up to 50 payloads. AUDIT: generate compliance summary report.
- `payload` (string): The flagged payload to analyse. Required for REPORT mode.
- `payloads` (array): Array of data payloads to classify. Required for BATCH mode. Maximum 50.

Output parameters:

- `_disclaimer` (string)
- `checked_at` (string)
- `message` (string)
- `mode` (string)
- `patterns_detected` (array)
- `status` (string): Present on the free-tier REPORT preview path
- `upgrade_url` (string)

### `validate_data_safety_lite` (~215 tokens)

Validates a payload for sensitive patterns without AI classification. Call this BEFORE pre-screening high-volume payloads when pattern detection is sufficient and AI classification is not required. Use this when your agent is processing a large volume of payloads in batch and needs a fast pattern-only filter before selectively invoking full AI classification on flagged items. Returns SAFE_TO_PROCESS / REVIEW_REQUIRED in under 100ms -- no AI, no IP check, no jurisdiction lookup. Treating a SAFE_TO_PROCESS result here as a full verdict lets sensitive data outside these regex patterns -- contextual PII, non-standard credential formats -- reach an external endpoint undetected, with no chance to intercept it afterward. Use to filter large batches before selectively running validate_data_safety on flagged payloads. Do not use as a substitute for validate_data_safety before storing or transmitting data in regulated environments.

Input parameters:

- `context` (string): Optional: what your agent plans to do with this data.
- `payload` (string, required): The data payload to screen for sensitive patterns.

Output parameters:

- `_disclaimer` (string)
- `agent_action` (string)
- `analysis_type` (string)
- `checked_at` (string)
- `patterns_detected` (array)
- `sensitivity_level` (string)
- `verdict` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp-production#diagnostics

## Score history

- 2026-08-03: 54
- 2026-08-02: 54
- 2026-08-01: 53
- 2026-07-31: 53
- 2026-07-30: 51
- 2026-07-29: 51
- 2026-07-28: 50
- 2026-07-27: 49
- 2026-07-26: 49

## Links

- Remote endpoint: https://data-compliance-mcp-production.up.railway.app/
- Repository: https://github.com/OjasKord/data-compliance-mcp
- Website: https://kordagencies.com/
- Changelog RSS feed: https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ojaskord-data-compliance-mcp/data-compliance-mcp-production