Skip to main content
Glama
repo-security-scan-mcp

repo-security-scan-mcp

by sahan411

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

scan_repo

Scans a folder; returns counts and findings ordered by severity (path, min_severity, limit, max_mb).

triage_summary

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 test

Add 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 tools
scan_repoScan a local repo for AI-built-app security problemsA
Read-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 scanA
Read-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

    A3.7/5.0

    Scored across 2 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Static 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.
      5
      29 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT