Data Compliance Classifier MCP

io.github.OjasKordPublished by GitHub account OjasKordv1.0.25Updated Oct 24, 2026

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

The publisher's own server: classifier.dev

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Checks a data payload for PII, PHI, PCI and credential patterns and returns a compliance verdict before an agent stores or shares it.

What you can do
Validate a payload against GDPR, HIPAA, PCI-DSS and other frameworks and get a verdict, sensitivity level, detected categories and applicable regulations, optionally with jurisdiction from an IP address and a credential breach check. Retrieve a detailed compliance report and remediation strategy for a flagged payload. Run fast pattern-only screening on high-volume batches without AI classification or IP lookup. Generate batch classifications and audit-style compliance reports on the paid tier.
When to use it
Useful when an agent handles customer, health, payment or credential data and you want a pre-action check before it writes to a database, logs, or sends data to a third-party API. The lite tool suits bulk pre-screening; the report tool suits deciding whether to proceed, redact or halt.
Requirements
Runs as a remote HTTP endpoint or as a local npm package over stdio. The free tier needs no API key; the paid tier uses an x-api-key header. The local package requires an ANTHROPIC_API_KEY, and optionally an ABUSEIPDB_API_KEY for threat intelligence. Network access to the endpoint and its upstream services is needed.
Before you install
Payloads are sent to a third-party service and on to Claude AI, IPinfo, HaveIBeenPwned and AbuseIPDB; the README says payloads are not stored or logged, but sensitive data still leaves your environment. Paid bundles cost money, and the README states classification is informational only and not legal advice or a compliance guarantee.

Installation

In SourceWeft

  1. Open Data Compliance Classifier MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.OjasKord%2Fdata-compliance-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

[smithery badge]

Data Compliance Classifier MCP

[ToolRank]

Your agent is about to store customer data. Is it safe to? This tool tells you in one call.

What it does

Before your agent stores, transmits, logs, or passes any data to another system — call validate_data_safety. Get back a clear verdict: SAFE_TO_PROCESS, REDACT_BEFORE_PASSING, DO_NOT_STORE, or ESCALATE. Your agent acts on the verdict immediately. No human interpretation needed.

Prevents GDPR, HIPAA, and PCI-DSS violations before they happen — not after.

Why this exists

Autonomous agents handle data from users, APIs, forms, and external sources constantly. Most agents process that data without checking whether they should. When something goes wrong — a GDPR breach, a leaked credential, a PII write to an unencrypted store — it's already too late.

This tool gives agents a pre-action safety check. One call, clear verdict, agent proceeds or halts.

Tools

validate_data_safety (free tier)

Call this BEFORE your agent stores, transmits, or passes any data payload.

Input:

  • payload — the data to classify (any string, JSON, form data, API response)
  • context — what your agent is about to do with it (improves accuracy)
  • data_origin_ip — optional IP for jurisdiction detection (GDPR if EU, CCPA if US, etc.)
  • jurisdiction — optional override if IP unavailable

Output:

  • verdict — SAFE_TO_PROCESS / REDACT_BEFORE_PASSING / DO_NOT_STORE / ESCALATE
  • sensitivity_level — PUBLIC / INTERNAL / CONFIDENTIAL / RESTRICTED
  • detected_categories — PII, PHI, PCI, CREDENTIALS, FINANCIAL, LOCATION, etc.
  • applicable_regulations — GDPR, HIPAA, PCI-DSS, CCPA, PIPEDA, LGPD, etc.
  • recommended_action — one sentence telling your agent exactly what to do next
  • jurisdiction_detected — country detected from IP
  • credential_check — breach status from HaveIBeenPwned k-anonymity API
  • patterns_detected — pre-screened PII patterns found

get_safety_report (paid tier)

Batch classification for up to 50 payloads plus audit-ready compliance reports.

Modes:

  • BATCH — classify multiple payloads with full AI reasoning + AbuseIPDB threat intelligence
  • AUDIT — generate a structured compliance report for a dataset description

validate_data_safety_lite (free tier)

Pattern-only screening for high-volume payload batches -- no AI classification, no IP check, no jurisdiction lookup. Returns SAFE_TO_PROCESS / REVIEW_REQUIRED in under 100ms. Use to filter large batches before selectively running validate_data_safety on flagged items.

Data privacy

We do not store or log your data payloads. All payloads are analysed in memory and immediately discarded. Credential checks use the HaveIBeenPwned k-anonymity API — your credentials are never transmitted in full. Only the first 5 characters of a SHA-1 hash are sent.

Data sources

  • Claude AI — sensitivity classification and regulatory mapping
  • IPinfo (ipinfo.io) — jurisdiction detection from IP address
  • HaveIBeenPwned (haveibeenpwned.com) — credential breach checking via k-anonymity
  • AbuseIPDB (abuseipdb.com) — IP threat intelligence (paid tier)

Pricing

PlanClassificationsPrice
Free20/monthNo API key needed
Starter500-call bundle$24
Pro2,000-call bundle$84

Upgrade at kordagencies.com

Quick start

No API key needed for free tier:

json
{  "data-compliance": {    "url": "https://data-compliance-mcp-production.up.railway.app"  }}

With paid API key:

json
{  "data-compliance": {    "url": "https://data-compliance-mcp-production.up.railway.app",    "headers": {      "x-api-key": "your_api_key_here"    }  }}

Harness Integration

Claude Code / Claude Desktop (.mcp.json)

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

LangChain (Python)

python
from langchain_mcp_adapters.client import MultiServerMCPClientclient = MultiServerMCPClient({    "data-compliance": {        "url": "https://data-compliance-mcp-production.up.railway.app",        "transport": "http"    }})tools = await client.get_tools()

OpenAI Agents SDK (Python)

python
from agents import Agent, HostedMCPToolagent = Agent(    name="Assistant",    tools=[HostedMCPTool(tool_config={        "type": "mcp",        "server_label": "data-compliance",        "server_url": "https://data-compliance-mcp-production.up.railway.app",        "require_approval": "never"    })])

LangGraph

Same as LangChain above — langchain-mcp-adapters works with LangGraph natively.

Example call

bash
curl -X POST https://data-compliance-mcp-production.up.railway.app \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"validate_data_safety","arguments":{"payload":"{\"name\":\"John Smith\",\"email\":\"[email protected]\",\"dob\":\"1985-03-12\",\"address\":\"14 Baker Street, London\"}","context":"write to customer database","jurisdiction":"EU"}}}'

Expected response:

json
{  "verdict": "DO_NOT_STORE",  "sensitivity_level": "RESTRICTED",  "detected_categories": ["PII"],  "applicable_regulations": ["GDPR"],  "recommended_action": "Do not store without explicit consent and a documented lawful basis under GDPR Article 6.",  "jurisdiction_detected": "EU"}

Legal

Classification is AI-powered and for informational purposes only. Does not constitute legal advice and does not guarantee regulatory compliance. Full terms: kordagencies.com/terms.html

Source: README.md at commit 3a35de1

Tools

3

validate_data_safety

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.

Parameterscontextpayloadrequiredjurisdictiondata_origin_ip

get_safety_report

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.

Parametersmoderequiredcontextpayloadpayloadsjurisdictiondataset_description

validate_data_safety_lite

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.

Parameterscontextpayloadrequired

Version history

1
  1. v1.0.25LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Classifier integrations