Data Compliance Classifier MCP
REMOTE · DATA-COMPLIANCE-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3
Classify data safety before storing or sharing. GDPR, HIPAA, PCI-DSS, CCPA. AI-powered.
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability32
- AI-judged instruction clarity (fair).Partial
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · data-compliance-mcp-production.up.railway.app
claude mcp add --transport http ojaskord-data-compliance-mcp https://data-compliance-mcp-production.up.railway.app/
[mcp_servers.ojaskord-data-compliance-mcp] url = "https://data-compliance-mcp-production.up.railway.app/"
{
"$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 mcp add ojaskord-data-compliance-mcp --url https://data-compliance-mcp-production.up.railway.app/ --transport streamable-http
mcp_servers:
ojaskord-data-compliance-mcp:
url: "https://data-compliance-mcp-production.up.railway.app/" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +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.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://data-compliance-mcp-production.up.railway.app
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of data-compliance-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://data-compliance-mcp-production.up.railway.app | Verified | 200 | |
| http (plaintext) | http://data-compliance-mcp-production.up.railway.app | HTTPS enforced | 301 | https://data-compliance-mcp-production.up.railway.app/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_safety_report ~341
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | — |
| checked_at | string | yes | — |
| message | string | — | — |
| mode | string | — | — |
| patterns_detected | array | — | — |
| status | string | — | Present on the free-tier REPORT preview path |
| upgrade_url | string | — | — |
No examples provided.
validate_data_safety ~388
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | — |
| analysis_type | string | — | — |
| applicable_regulations | array | — | — |
| checked_at | string | yes | — |
| 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 | yes | — |
| source_url | string | — | — |
| verdict | string | yes | — |
No examples provided.
validate_data_safety_lite ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Optional: what your agent plans to do with this data. |
| payload | string | yes | The data payload to screen for sensitive patterns. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | — |
| agent_action | string | yes | — |
| analysis_type | string | — | — |
| checked_at | string | yes | — |
| patterns_detected | array | — | — |
| sensitivity_level | string | — | — |
| verdict | string | yes | — |
No examples provided.