Skip to main content
Glama

Related Servers

Alternatives to pdpa-audit-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Scan 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.
      3
      54 npm
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Exposes 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.
      7
      MIT

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues