
Compliance Checker
io.github.4hmetuyarPublished by GitHub account 4hmetuyarv0.2.4Updated Nov 10, 2026
KVKK/GDPR/CCPA compliance checks for codebases
Overview
Runs KVKK, GDPR and CCPA compliance checks on sites and codebases, scores privacy policies, and compares legal requirements.
- What you can do
- Start compliance scans for a URL and fetch findings filtered by framework and severity (requires API key)
- Analyze a privacy policy URL for 10 signals, a 0-100 score and a letter grade
- List legal requirements for KVKK, GDPR and CCPA with article references
- Compare common and differing articles across the three frameworks
- Detect cookie consent platforms such as OneTrust and Cookiebot
- When to use it
- Useful when you need a quick privacy or data-protection review of a website or codebase, want a privacy policy scored against common signals, or need to see how KVKK, GDPR and CCPA requirements differ.
- Requirements
- Local Node.js process installed from the npm package, run via npx or globally. A GuardBee API key in GUARDBEE_API_KEY is required for the scan and findings tools; the other three tools work without it. GUARDBEE_BASE_URL optionally overrides the default endpoint. Network access to the GuardBee service.
Installation
In SourceWeft
- Open Compliance Checker in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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=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.
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_frameworkswork offline
Quick Start
Add to claude_desktop_config.json:
Get your API key at app.guardbee.ai/developers.
MCP Tools
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
Supported Frameworks
Privacy Policy Scoring
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)
Environment Variables
Development
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.
Source: packages/compliance-checker/README.md at commit 040e072
Tools
0Version history
1- v0.2.4LatestSep 29, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts