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.
urlrequiredwaitframeworkrequired
io.github.GuardBeePublished by GitHub account GuardBeev0.4.1Updated Nov 3, 2026
KVKK/GDPR/CCPA compliance checks for codebases
Runs KVKK, GDPR and CCPA compliance scans on URLs via the GuardBee API, analyzes privacy policies, and compares legal requirements.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
🇬🇧 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=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare replaced with a placeholder. See@guardbee/mcp-telemetry.
A GuardBee API key is required for the
check_complianceandget_compliance_findingstools. Get one at app.guardbee.ai/developers.
analyze_privacy_policy, list_requirements, compare_frameworks work offlineAdd to claude_desktop_config.json:
Get your API key at app.guardbee.ai/developers.
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"
The analyze_privacy_policy tool looks for 10 signals in the policy text:
Grades: A (90-100) · B (75-89) · C (60-74) · D (45-59) · F (0-44)
MIT — GuardBee
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.
Source: packages/compliance-checker/README.md at commit bc5997d
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.
urlrequiredwaitframeworkrequiredGet compliance findings from a completed GuardBee scan, optionally filtered by severity
scanIdrequiredseverityframeworkFetch and analyze a privacy policy page for completeness against GDPR/KVKK requirements. Works without an API key.
urlrequiredList all compliance requirements for a framework with legal basis references
severityframeworkrequiredCompare KVKK, GDPR, and CCPA requirements side by side to understand overlaps and gaps
Takes no parameters.
90% 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.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npm install -g @guardbee/mcp-compliance-checker{ "mcpServers": { "guardbee-compliance-checker": { "command": "npx", "args": ["-y", "@guardbee/mcp-compliance-checker"], "env": { "GUARDBEE_API_KEY": "gb_..." } } }}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.npm installnpm test # unit testsnpm run build # TypeScript compile