CertScore.Ai — Light Mode MCP Server

Connect CertScore.Ai — Light Mode to Claude, Cursor or any other MCP client and it stops being a tab you switch to. No-account public website privacy risk scans with 20 new scans/day and free recent-result reuse. The certscore.ai — light mode mcp server is what makes that connection.

What the server does

CertScore (certscore.ai) is a production-minded MVP for scanning public websites for potential accessibility, privacy, cookie, policy, and disclosure risk signals. It is a risk signal and monitoring product, not a legal certification platform.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• scanner — generated PDF generation and upload
• NEXT_PUBLIC_APP_URL — DATABASE_URL
• BETTER_AUTH_SECRET — GOOGLE_CLIENT_ID
• GOOGLE_CLIENT_SECRET — S3_BUCKET
• S3_REGION — S3_ACCESS_KEY_ID
• DATABASE_URL — OPENAI_API_KEY
• WORKER_CONCURRENCY — PLAYWRIGHT_BROWSERS_PATH
• VALIDATION_OPENAI_MODEL — VALIDATION_NANO_MODEL
• WEB_BOT_AUTH_ENABLED — WEB_BOT_AUTH_PRIVATE_KEY_PEM
• pnpm — -filter @website-signal-risk-scanner/validation-worker exec playwright install chromium
• worker-scan-pipeline — tests runs on pushes to main, pull requests, and manual dispatch. It installs Chromium, typechecks validation-worker, and runs pnpm
• live-validation — smoke runs after the deterministic job and executes pnpm --filter @website-signal-risk-scanner/validation-worker smoke:validation only when the

Credentials and setup notes

Configuration is passed through the environment: NEXT_PUBLIC_APP_URL, DATABASE_URL, BETTER_AUTH_SECRET, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY, OPENAI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch CertScore.Ai — Light Mode.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. CertScore.Ai — Light Mode's toolset — scanner, NEXT_PUBLIC_APP_URL, BETTER_AUTH_SECRET and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ai.certscore; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.