Skip to main content
Glama
larik15

supabase-security-mcp

by larik15

Related Servers

Alternatives to supabase-security-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Audits PostgreSQL/Supabase schemas for security issues like missing RLS, permissive policies, and sensitive data exposure during AI conversations.
      3
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that lets AI coding agents (Claude Code, Cursor, Cline) audit Supabase projects for security misconfigurations AND apply the fixes — without leaving the agent. Tools: audit_project, list_findings, preview_fix (BEGIN/ROLLBACK safety), apply_fix (with confirmation), apply_all_fixes (transactional bulk). Closes the audit-fix loop entirely in the agent — other Supabase scanners only report.
      5
      2 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to run read-only AWS security audits and receive normalized, severity-ranked findings about account posture, such as stale access keys, missing MFA, public buckets, open security groups, and CloudTrail coverage.
      11
      15 PyPI
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Enables security auditing, penetration testing, and compliance validation with tools like Semgrep, Trivy, Gitleaks, and OWASP ZAP. Features strict project boundary enforcement and supports OWASP, CIS, and NIST compliance frameworks.
      7
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables code auditing, scanning for committed secrets and vulnerable dependencies, and generating self-review checklists, with optional paid audit pricing.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables authorized security auditing of AI-agent supply chains and agent-facing surfaces: deterministic local skill-bundle audits against eight attack patterns, secrets scanning, and scope-gated read-only recon of agent endpoints and MCP surfaces.
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The probes are differentiated: `probe_anon` is black-box REST exposure, `audit_policies` inspects database catalogs, `two_account_test` verifies cross-user isolation, and `security_report` orchestrates. There is some conceptual overlap between `probe_anon` and `audit_policies` around anon/RLS exposure, so an agent might briefly hesitate, but no tool duplicates another.

    Naming Consistency3/5

    `probe_anon` and `audit_policies` follow a verb_noun command style, while `two_account_test` and `security_report` are noun-style names. They are all readable snake_case, but the action-first convention is not applied consistently across the set.

    Tool Count5/5

    Four tools is appropriate for a focused Supabase security-audit server: three distinct probes plus one report aggregator. Each tool has a clear job, and none feels redundant or missing.

    Completeness4/5

    The set covers anon REST exposure, RLS policy misconfigurations, SECURITY DEFINER functions, and cross-user table isolation, which are the core Supabase data-security risks. Minor gaps remain, such as no dynamic storage-object cross-account test and no anonymous INSERT probe, but static policy checks partially compensate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues