Data Compliance Classifier MCP

io.github.OjasKord由 GitHub 账号 OjasKord 发布v1.0.25更新于 Oct 24, 2026

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

发布方自己的服务:classifier.dev

已验证Streamable HTTP可网页运行安全与监控数据与分析

概览

AI 生成的概览

检查数据载荷中的个人、健康、支付与凭据信息,在智能体存储或共享前返回合规判定。

可以做什么
按 GDPR、HIPAA、PCI-DSS 等框架校验载荷,返回判定、敏感级别、识别到的类别与适用法规,可选依据 IP 判断司法辖区并检查凭据是否泄露。为被标记的载荷获取详细合规报告与整改建议。对大批量载荷做仅模式匹配的快速筛查,不做 AI 分类与 IP 查询。付费版可批量分类并生成审计式合规报告。
适用场景
适用于智能体处理客户、健康、支付或凭据数据,并希望在写入数据库、记录日志或发送给第三方 API 之前先做检查的场景。轻量工具适合批量预筛,报告工具适合决定继续、脱敏还是中止。
运行要求
可作为远程 HTTP 端点运行,也可作为本地 npm 包通过 stdio 运行。免费版无需 API 密钥,付费版使用 x-api-key 请求头。本地包需要 ANTHROPIC_API_KEY,可选 ABUSEIPDB_API_KEY 用于威胁情报。需要访问该端点及其上游服务的网络。
安装前请注意
载荷会发送到第三方服务,并进一步传给 Claude AI、IPinfo、HaveIBeenPwned 和 AbuseIPDB;README 称不存储、不记录载荷,但敏感数据仍会离开你的环境。付费套餐需要花钱,README 也说明分类仅供参考,不构成法律意见,也不保证合规。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Data Compliance Classifier MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.OjasKord%2Fdata-compliance-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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

来源:README.md,提交 3a35de1

工具

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.

输入参数contextpayload必填jurisdictiondata_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.

输入参数mode必填contextpayloadpayloadsjurisdictiondataset_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.

输入参数contextpayload必填

版本历史

1
  1. v1.0.25最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Classifier 集成