repo-security-scan-mcp
Scans local Express apps for security issues such as wildcard CORS, string-built SQL, shell injection, and API routes that mutate data without an auth check.
Detects open Firebase security rules in the scanned project.
Scans local Next.js projects for common security problems, including secrets exposed to the browser through NEXT_PUBLIC_ variables, API routes that change data without a visible auth check, and dangerous code patterns such as dangerouslySetInnerHTML.
Flags Supabase tables without row-level security and leaked Supabase service_role JWTs found in the scanned project.
Scans local Vite projects for secrets exposed to the browser through VITE_ environment variables, alongside other leaked-secret and unsafe-code findings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@repo-security-scan-mcp scan ./my-app for security issues before launch"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
repo-security-scan-mcp
An MCP server that lets Claude (or any MCP client) triage a local project for the classic security problems in AI-built web apps (Next.js, Vite, Express, Supabase, Firebase and similar).
It reads a folder you point it at. It never opens network connections and never probes live sites. Secrets in results are redacted to their first 4 characters.
What it checks (20+ rule types)
Leaked secrets (AWS, Stripe, GitHub, OpenAI/Anthropic-style, Slack, SendGrid, private keys, database URLs with passwords, JWTs including Supabase service_role), secrets exposed to the browser through NEXT_PUBLIC_/VITE_ variables, Supabase tables without row-level security, open Firebase rules, wildcard CORS, dangerous code patterns (eval, dangerouslySetInnerHTML, string-built SQL, shell injection), API routes that change data without a visible auth check, weak JWT secrets, weak password hashing, debug mode left on, TLS verification turned off, committed .env files, unpinned dependencies, missing lockfile and missing tests.
Related MCP server: web3_auth_scan
Tools
Tool | What it does |
| Scans a folder; returns counts and findings ordered by severity ( |
| Same scan, returned as a short plain-English go/no-go with what to fix first. |
Install and use
Requires Node 18+ and Python 3.
git clone <this repo> && cd repo-security-scan-mcp
npm install
npm testAdd to Claude Desktop (claude_desktop_config.json) or Claude Code (claude mcp add):
{ "mcpServers": { "repo-security-scan": { "command": "node", "args": ["/absolute/path/to/server.mjs"] } } }Set PYTHON if your Python executable is not python (Windows) or python3 (macOS/Linux).
Then ask: "Scan ./my-app and tell me what to fix before launch."
Honest limits
This is a heuristic static scan, not a penetration test. It produces false positives and misses issues. Review each finding before acting, and rotate any exposed secret immediately. npm test runs a real MCP client against generated fixture apps (fake secrets are assembled at runtime so this repo never contains token-shaped strings): 7 checks, including "clean app has 0 HIGH findings".
Need this on your project, or a custom MCP server for your tools?
Open an issue or message the author.
License: MIT
Available Tools
2 toolsscan_repoScan a local repo for AI-built-app security problemsARead-onlyIdempotent
Scans a local project folder (Next.js, Vite, Express, Supabase, Firebase style) for leaked secrets, secrets exposed to the browser, missing Supabase row-level security, wildcard CORS, open Firebase rules, dangerous code patterns and API routes without a visible auth check. Returns counts plus findings ordered by severity. Secrets are redacted.
Inputs: path (required), limit, max_mb, min_severity.
triage_summaryOne-paragraph triage of a repo scanARead-onlyIdempotent
Runs the same scan and returns a short plain-English triage: what to fix first and why. Good for a quick go/no-go before deploying.
Inputs: path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
scan_repo and triage_summary both run 'the same scan', so their boundaries are blurry; the distinction is purely output format (raw findings by severity vs. plain-English prioritization). An agent wanting a prioritized answer versus full findings has some guidance, but the overlap invites misselection.
Both names use snake_case and are readable, but scan_repo is a clear verb_noun while triage_summary is a noun phrase (verb/domain mix). Minor deviation within an otherwise consistent style.
Two tools for a full security scanner is on the thin side. The scan/summarize pair covers the headline workflow, but there is no room for narrower operations like scanning a single file or listing rule metadata.
Core scan-and-report is present, but notable gaps exist: no way to fetch details for a single finding, filter/ignore rules, manage a baseline, or run in a CI-oriented mode. Agents can work around these by re-running scans, but the lifecycle is partial.
Maintenance
Related MCP Connectors
Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.
Scan a deployed app URL for exposed keys, open Supabase tables and missing security headers.
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Scan a site or AI-built app for exposed databases, keys and MCP endpoints, then verify the fixes.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to run static heuristic scans over a repository path via stdio, surfacing review candidates with file:line evidence for web3 auth and payment vulnerability patterns. Results can be used as CI-style gates or triage input without any dataflow analysis or external dependencies.MIT
- AlicenseAqualityBmaintenanceStatic security scanner for AI-generated (vibe-coded) Supabase and Next.js apps. Runs as an MCP server so an LLM can scan, explain findings, and produce fixes while it writes code, all locally and offline.529 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run deterministic, read-only local repository audits for risky GitHub workflows, undocumented environment variables, possible credentials, and conflicting dependency configuration, returning structured findings without sending source code to a service.43 npmMIT