Skip to main content
Glama
DarkLens Compliance & Dark Pattern Auditor

DarkLens Compliance & Dark Pattern Auditor

DarkLens MCP Server πŸ€–πŸ”

Real-time deceptive design and dark pattern compliance auditor for AI coding agents.

npm version License: MIT

DarkLens MCP connects Cursor, Windsurf, Claude Desktop, Antigravity, Lovable, v0, and Cline directly to the DarkLens compliance auditing engine. Your AI coding agent can automatically audit staging URLs, check newly generated JSX/HTML components for deceptive patterns (GDPR, FTC Act Sec. 5, CCPA, EU DSA), and fix non-compliant UI before code is committed.


⚑ Quickstart Configuration by Coding Agent

1. πŸ–±οΈ Cursor

  1. Go to Cursor Settings (Ctrl + , or Cmd + ,) β†’ Features β†’ MCP.

  2. Click + Add New MCP Server.

  3. Fill in:

    • Name: darklens

    • Type: command

    • Command: npx -y darklens-mcp

    • Environment Variables: DARKLENS_API_KEY=dl_live_YOUR_KEY

  4. In Cursor Chat or Composer, prompt:

    "@darklens audit my checkout page and fix any illegal dark patterns."


2. 🌊 Windsurf (Codeium)

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "darklens": {
      "command": "npx",
      "args": ["-y", "darklens-mcp"],
      "env": {
        "DARKLENS_API_KEY": "dl_live_YOUR_KEY"
      }
    }
  }
}

3. 🧠 Claude Desktop / Claude Code (Anthropic)

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "darklens": {
      "command": "npx",
      "args": ["-y", "darklens-mcp"],
      "env": {
        "DARKLENS_API_KEY": "dl_live_YOUR_KEY"
      }
    }
  }
}

4. πŸš€ Antigravity (Google / DeepMind)

Add to your Antigravity MCP settings or call via native MCP config:

{
  "mcpServers": {
    "darklens": {
      "command": "npx",
      "args": ["-y", "darklens-mcp"],
      "env": {
        "DARKLENS_API_KEY": "dl_live_YOUR_KEY"
      }
    }
  }
}

5. ❀️ Lovable & v0 / Bolt.new

In Lovable, Bolt.new, or v0 terminal or agent custom tool integrations, execute:

npx -y darklens-mcp --key dl_live_YOUR_KEY

Or instruct the agent to run DarkLens CLI on preview URLs:

npx darklens <your-preview-url> --key $DARKLENS_API_KEY

6. πŸ’» VS Code (Cline / Roo Code)

  1. Open the Cline / Roo Code sidebar tab.

  2. Click the MCP icon β†’ Configure MCP Servers.

  3. Add:

{
  "mcpServers": {
    "darklens": {
      "command": "npx",
      "args": ["-y", "darklens-mcp"],
      "env": {
        "DARKLENS_API_KEY": "dl_live_YOUR_KEY"
      }
    }
  }
}

Related MCP server: pageguard-mcp

πŸ› οΈ Exposed MCP Tools

Tool

Description

darklens_audit_url

Audits any public or staging URL. Returns compliance score (0-100), pass/fail, and full findings with legal citations.

darklens_audit_html

Audits raw HTML/JSX markup generated by the AI agent before it writes files to disk.

darklens_get_fair_pattern_guide

Returns exact compliant alternatives and regulatory articles for any pattern (e.g. forced_continuity, confirmshaming).


πŸ”‘ Authentication

Every request requires a DarkLens API key (dl_live_...). Get your key at darklens.dev/dashboard.


πŸ“„ License

MIT Β© DarkLens

Available Tools

3 tools
darklens_audit_htmlA

Audit raw HTML, JSX, or component markup for dark patterns (pre-checked auto-renewal checkboxes, confirmshaming guilt copy, fake countdown timers, hidden fees, missing reject buttons) before committing to production.

Inputs: rawHtml (required), url, failOn, threshold.

darklens_audit_urlA

Audit any staging or live URL for deceptive dark patterns, compliance risks (FTC, GDPR, CCPA, EU DSA), and sneaky checkout traps. Returns compliance score (0-100), pass/fail, and detailed findings with remediation fixes.

Inputs: url (required), failOn, threshold.

darklens_get_fair_pattern_guideA

Retrieve regulatory compliance rules, legal citations (FTC Act Sec. 5, GDPR Art. 25, EU DSA Art. 25, CCPA), and compliant UI/UX alternatives for specific deceptive design categories.

Inputs: patternCategory.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools are cleanly separated by input type and purpose: auditing a live URL, auditing raw markup, and retrieving reference guidance. An agent can pick the right tool from the target artifact alone, with no overlap between them.

    Naming Consistency5/5

    All names use a uniform darklens_ prefix plus consistent verb_noun structure (audit_url, audit_html, get_fair_pattern_guide). The convention is predictable and the intent is readable from the name.

    Tool Count4/5

    Three tools map neatly to the domain's core actions (live audit, pre-commit audit, reference lookup), so nothing feels padded. It is slightly thinβ€”no batch, history, or export toolsβ€”but the scope is deliberately focused rather than incomplete by accident.

    Completeness4/5

    The audit lifecycle is covered from both a live-URL and a pre-production markup angle, plus a knowledge lookup for remediation, which suits the stated purpose well. Minor gaps exist around saving/comparing past audits or exporting reports, but agents can work around them by re-running audits.

    Related MCP Connectors

    Related MCP Servers