Data Compliance Classifier MCP
NPM · DATA-COMPLIANCE-MCP · 2 COMPONENTS · SCANNED SEP 20
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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 865 tokens (~288/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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Data Compliance Classifier MCP server?
Data Compliance Classifier MCP runs locally as an npm package, launched with npx -y data-compliance-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · data-compliance-mcp
claude mcp add ojaskord-data-compliance-mcp -- npx -y data-compliance-mcp
{
"mcpServers": {
"ojaskord-data-compliance-mcp": {
"command": "npx",
"args": [
"-y",
"data-compliance-mcp"
]
}
}
} {
"servers": {
"ojaskord-data-compliance-mcp": {
"command": "npx",
"args": [
"-y",
"data-compliance-mcp"
]
}
}
} codex mcp add ojaskord-data-compliance-mcp -- npx -y data-compliance-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ojaskord-data-compliance-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"data-compliance-mcp"
],
"enabled": true
}
}
} openclaw mcp add ojaskord-data-compliance-mcp --command npx --arg -y --arg data-compliance-mcp
mcp_servers:
ojaskord-data-compliance-mcp:
command: "npx"
args: ["-y", "data-compliance-mcp"] {
"McpServers": {
"ojaskord-data-compliance-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"data-compliance-mcp"
]
}
}
} assistant mcp add ojaskord-data-compliance-mcp -t stdio -c npx -a -y data-compliance-mcp
{
"mcpServers": {
"ojaskord-data-compliance-mcp": {
"command": "npx",
"args": [
"-y",
"data-compliance-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/data-compliance-mcp@1.0.25
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_safety_report ~306
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. 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 ~171
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. 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.
What is the Data Compliance Classifier MCP server?
Data Compliance Classifier MCP is listed in the public MCP registry as io.github.OjasKord/data-compliance-mcp. Classify data safety before storing or sharing. GDPR, HIPAA, PCI-DSS, CCPA. AI-powered. This page covers its npm package (data-compliance-mcp).
Is the Data Compliance Classifier MCP server safe to use?
Data Compliance Classifier MCP scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Data Compliance Classifier MCP server expose?
Data Compliance Classifier MCP exposes 3 tools: validate_data_safety, get_safety_report, validate_data_safety_lite. Their descriptions and schemas cost roughly 865 tokens of context every time the server is loaded.
Is the Data Compliance Classifier MCP server still maintained?
Data Compliance Classifier MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Data Compliance Classifier MCP server under?
Data Compliance Classifier MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.