pdpa-audit-mcp
Related Servers
Alternatives to pdpa-audit-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI-assisted compliance scanning of codebases for GDPR, CCPA, WCAG, PCI-DSS, HIPAA, EU AI Act, and other regulations, providing risk scores, fine estimates, and suggested fixes within MCP-compatible IDEs.-
- AlicenseAqualityBmaintenanceEnables AI coding agents to generate LGPD-compliant cookie banners by detecting trackers in local projects, and to scan published sites for privacy violations, returning actionable results.18447 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables MCP-compatible assistants to query Ecuadorian legislation and perform local static audits of software repositories for privacy, security, and compliance risks.66 npm5MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.86 npmMIT

pageguard-mcpofficial
AlicenseAqualityDmaintenanceScan any project or website for privacy compliance issues directly in your AI coding tool. Detects tracking tech, cookies, and third-party data collection. Works in Claude Code, Cursor, and Windsurf.354 npm1MIT- AlicenseBqualityBmaintenanceExposes seven MCP tools that let an AI coding agent detect a project's stack, fetch the priority security checks for that platform, search 2,057 OWASP-derived check cards with file-and-commit provenance, and record evidence-backed pass/fail results in a report.7MIT
TDQS
Scored across 9 tools
Each tool targets a distinct audit surface: privacy policy text, cookie consent markup, web forms, local project files, breach documentation, third-party domains, plus aggregation/reporting/checklist tools. The only mild overlap is run_full_audit versus the individual scan tools, but that granular-vs-aggregate split is a standard and understandable pattern.
All nine tools follow a strict snake_case verb_noun pattern (scan_*, detect_*, find_*, check_*, run_*, generate_*, list_*). Verb variation is semantically meaningful rather than arbitrary, so the naming stays predictable.
Nine tools is well within the ideal range and each earns its place: six specific audit checks, one orchestrator, one report generator, and one reference/checklist tool. Nothing feels padded or missing at the count level.
The surface covers the full audit lifecycle from individual checks through full audit to gap reporting, plus a checklist reference. Minor gaps remain: no tool to retrieve or persist prior audit results, no remediation/fix guidance beyond the gap report, and no explicit data subject request workflow check.