Compliance Checker

io.github.GuardBee由 GitHub 账号 GuardBee 发布v0.4.1更新于 Nov 3, 2026

KVKK/GDPR/CCPA compliance checks for codebases

概览

AI 生成的概览

通过 GuardBee API 对网址执行 KVKK、GDPR 和 CCPA 合规扫描,分析隐私政策并比较各法规要求。

可以做什么
  • 针对 KVKK、GDPR 或 CCPA 对网址执行完整合规扫描,返回差距分析与行动计划
  • 获取已完成扫描的结果,可按法规框架或严重程度筛选
  • 抓取隐私政策页面并按十项合规信号打分并给出等级
  • 列出各法规框架的具体要求及法条依据
  • 并排比较 KVKK、GDPR 与 CCPA 的要求异同
适用场景
适合需要快速检查网站或其隐私政策的数据保护合规情况,或想了解 KVKK、GDPR 与 CCPA 要求差异的场景。要求清单与框架比较无需账号即可使用。
运行要求
以 npm 包形式通过 stdio 在本机运行(需 Node.js)。扫描与结果查询工具需要环境变量 GUARDBEE_API_KEY 中的 GuardBee API 密钥,其余三个工具无需密钥。可用 GUARDBEE_BASE_URL 指定自定义端点。需要访问 GuardBee 服务的网络连接。
安装前请注意
扫描与结果查询工具会把目标网址发送给 GuardBee API,并需要 GuardBee API 密钥;隐私政策工具会抓取所给网址。遥测默认关闭,但设置 GUARDBEE_TELEMETRY=1 后会向遥测包发送工具名、成功状态、耗时及文件路径等短参数值。结果仅为自动化信号,不构成法律意见。

安装

在 SourceWeft 中

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

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

@guardbee/mcp-compliance-checker

🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch

[npm version] [npm downloads] [License: MIT]

An MCP server that runs KVKK (Turkish data protection law), GDPR, and CCPA compliance checks via the GuardBee API, analyzes privacy policies, and compares legal requirements. Three of its tools work without an API key.

Telemetry is off by default. With GUARDBEE_TELEMETRY=1 it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields like content, token or password are replaced with a placeholder. See @guardbee/mcp-telemetry.

A GuardBee API key is required for the check_compliance and get_compliance_findings tools. Get one at app.guardbee.ai/developers.


Features

  • KVKK / GDPR / CCPA Scanning — triggers a compliance-focused scan via the GuardBee API and fetches findings
  • Privacy Policy Analysis — fetches policy text from a URL; 10 compliance signals, a score (0-100), and a letter grade
  • Cookie Banner Detection — detects OneTrust, Cookiebot, Axeptio, and 10+ CMP platforms
  • Requirements Catalog — 21 requirements with legal-article references across KVKK (9), GDPR (8), CCPA (4)
  • Framework Comparison — common and differing articles across KVKK / GDPR / CCPA
  • Key-Free Tools — analyze_privacy_policy, list_requirements, compare_frameworks work offline

Quick Start

bash
npm install -g @guardbee/mcp-compliance-checker

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "guardbee-compliance-checker": {      "command": "npx",      "args": ["-y", "@guardbee/mcp-compliance-checker"],      "env": {        "GUARDBEE_API_KEY": "gb_..."      }    }  }}

Get your API key at app.guardbee.ai/developers.


MCP Tools

ToolAPI KeyDescription
check_complianceRequiredStarts a compliance scan (KVKK/GDPR/CCPA) for a URL
get_compliance_findingsRequiredFetches scan findings, filterable by framework and severity
analyze_privacy_policyNoAnalyzes a privacy policy URL — score, grade, missing clauses
list_requirementsNoLists legal requirements for supported frameworks
compare_frameworksNoCompares similarities and differences across KVKK, GDPR, and CCPA

Example Usage

You can ask Claude:

"Check example.com's KVKK compliance"

"List GDPR requirements"

"Compare the differences between KVKK and GDPR"

"Analyze the privacy policy at https://example.com/privacy"

Example Output

Privacy Policy Analysis: https://example.com/privacy──────────────────────────────────────────────────────Score : 72/100  Grade: C
✅ Data controller identity disclosed✅ Purpose of processing stated✅ Retention periods mentioned✅ Cookie policy present❌ Legal basis for processing not stated❌ Data subject rights not listed (access, erasure, portability)❌ International transfer safeguards missing❌ Contact information for DPO missing
Recommendation: Add legal basis statements and data subject rights section.

Supported Frameworks

FrameworkRequirement CountScan Scenario
KVKK9kvkkFocus
GDPR8gdprFocus
CCPA4ccpaFocus

Privacy Policy Scoring

The analyze_privacy_policy tool looks for 10 signals in the policy text:

SignalDescription
Data controller identityCompany/organization name is stated
Purpose of processingWhy the personal data is being collected
Legal basisReference to GDPR Art. 6 / KVKK Art. 5
Retention periodsHow long the data will be kept
Data subject rightsAccess, erasure, portability, objection
Contact / DPOHow to reach the data controller
Cookie policyCookies and tracking technologies
Third-party sharingParties the data is shared with
Security measuresTechnical/administrative safeguards
International transferCross-border transfer safeguards

Grades: A (90-100) · B (75-89) · C (60-74) · D (45-59) · F (0-44)


Environment Variables

VariableDescription
GUARDBEE_API_KEYGuardBee API key (required for check_compliance and get_compliance_findings)
GUARDBEE_BASE_URLCustom endpoint (default: https://app.guardbee.ai)

Development

bash
npm installnpm test          # unit testsnpm run build     # TypeScript compile

License

MIT — GuardBee

Feedback

Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a ⭐ on the repository helps others find it.

来源:packages/compliance-checker/README.md,提交 bc5997d

工具

5

check_compliance

Run a full compliance scan for a URL against a regulatory framework (KVKK, GDPR, or CCPA) using the GuardBee scanner. Returns a gap analysis and action plan.

输入参数url必填waitframework必填

get_compliance_findings

Get compliance findings from a completed GuardBee scan, optionally filtered by severity

输入参数scanId必填severityframework

analyze_privacy_policy

Fetch and analyze a privacy policy page for completeness against GDPR/KVKK requirements. Works without an API key.

输入参数url必填

list_requirements

List all compliance requirements for a framework with legal basis references

输入参数severityframework必填

compare_frameworks

Compare KVKK, GDPR, and CCPA requirements side by side to understand overlaps and gaps

无需输入参数。

版本历史

3
  1. v0.4.1最新Oct 30, 2026
  2. v0.3.2Oct 22, 2026
  3. v0.2.5Oct 13, 2026

评分

已满足适用检查项的 90%

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

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分