DarkLens Compliance & Dark Pattern Auditor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DARKLENS_API_KEY | Yes | Your DarkLens API key (dl_live_...). Required for every request; get your key at https://darklens.dev/dashboard. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.