Skip to main content
MCP server CX Codex

Securealy — Claude Code MCP server: what it does, how to install

Securealy scores a site the way an attacker and a visitor would see it, flagging leaked keys and misconfigured backends with a letter grade.

Apache-2.0 updated 2026-10-24

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env SUPABASE_URL=<SUPABASE_URL> --env SUPABASE_SERVICE_KEY=<SUPABASE_SERVICE_KEY> --env SUPABASE_MGMT_TOKEN=<SUPABASE_MGMT_TOKEN> --env SUPABASE_PROJECT_REF=<SUPABASE_PROJECT_REF> --env STRIPE_SECRET_KEY=<STRIPE_SECRET_KEY> --transport stdio mcp -- npx -y securealy-mcp
Open on GitHub

What Securealy does

Securealy runs checks across TLS and security headers, secret keys leaked into client-side JavaScript bundles, cookie and CORS settings, SPF/DKIM/DMARC records, plus the state of Supabase and Stripe when they're wired into the project. Each run produces a letter grade broken down into blockers, failures, warnings and passes, with a link explaining each finding.

Three modes are available. The passive one works on any URL and mirrors what a regular browser sees — the home page, robots.txt, sitemap.xml. The verified mode needs proof of domain ownership through a DNS record, meta tag or file on the site, and adds checks for exposed .env and .git files, admin routes, and Supabase tables readable by the anon key. The local mode runs on the user's own machine with their own credentials and sends nothing out except the result the user chooses to share.

The MCP server needs environment variables matching whichever service it's checking: SUPABASE_URL and SUPABASE_SERVICE_KEY for Supabase, STRIPE_SECRET_KEY for Stripe, VERCEL_TOKEN for Vercel. Every run logs an entry to .securealy/history.json with the grade and failed checks, without the secret values themselves.

What it helps with

  • grade a site's security before putting it in front of real users
  • catch a secret key accidentally bundled into client-side JavaScript
  • check Supabase for tables exposed to the anon key
  • verify Stripe keys and webhook wiring match the live environment
  • grade an app that isn't deployed yet by pointing it at localhost

Example prompts for the agent

  • Run Securealy against my app and list every blocker
  • Check my Vercel environment variables and Stripe key through Securealy
  • Run the full local scan with check-rls and scan-repo

How to install Securealy

Platform CLI

claude mcp add --env SUPABASE_URL=<SUPABASE_URL> --env SUPABASE_SERVICE_KEY=<SUPABASE_SERVICE_KEY> --env SUPABASE_MGMT_TOKEN=<SUPABASE_MGMT_TOKEN> --env SUPABASE_PROJECT_REF=<SUPABASE_PROJECT_REF> --env STRIPE_SECRET_KEY=<STRIPE_SECRET_KEY> --transport stdio mcp -- npx -y securealy-mcp

Replace <…> with your own values. 7 more environment variables are in the server README

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about Securealy

How do I install Securealy in Claude Code?

Run `claude mcp add mcp -e SUPABASE_SERVICE_KEY=<SUPABASE_SERVICE_KEY> -e SUPABASE_MGMT_TOKEN=<SUPABASE_MGMT_TOKEN> -e STRIPE_SECRET_KEY=<STRIPE_SECRET_KEY> -e VERCEL_TOKEN=<VERCEL_TOKEN> -- npx -y securealy-mcp`.

What does Securealy do?

It grades a site against security, payment, email, domain and SEO checks, flags leaked keys and misconfigured Supabase or Stripe setups, and returns a letter grade with a breakdown of findings.

What's needed to check Supabase and Stripe?

Supabase checks need SUPABASE_URL and SUPABASE_SERVICE_KEY (or a management token and project reference), Stripe checks need STRIPE_SECRET_KEY; without those variables the related checks are skipped.

Similar MCP servers

All MCP servers for Security →

Project sponsors

Companies that keep this analytics open