Skip to main content
Glama

Related Servers

Alternatives to muhandis-rls-check

  • A
    license
    Not graded
    quality
    A
    maintenance
    This is an MCP server for PostgREST. It allows LLMs perform database queries and operations on Postgres databases via PostgREST. This server works with both Supabase projects (which use PostgREST) and standalone PostgREST servers.
    1,880 npm
    2,985
    Apache 2.0

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    Audits PostgreSQL/Supabase schemas for security issues like missing RLS, permissive policies, and sensitive data exposure during AI conversations.
    3
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI coding agents to audit Supabase or Postgres databases for Row Level Security and multi-tenant isolation holes, reading tables, grants, policies and functions for static findings and optionally probing those policies inside a rolled-back transaction. It reports each hole with an explanation and a fix, so an agent can verify the migrations it just wrote before declaring them done.
    1
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables AI coding assistants to check whether an API key is safe to expose, audit Supabase Row Level Security, generate owner-based RLS policy templates, and run a builder-specific pre-launch security checklist. Runs locally over stdio with no network calls, telemetry, or file access.
    5
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables safe, read-only SQL exploration and debugging on Supabase Edge Functions, respecting user JWTs. It inspects schemas, explains query plans, proposes RLS policies, and runs guarded queries without destructive operations.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to run read-only exposure scans against MCP servers that front databases, surfacing unauthenticated access, role/tool leaks, write-capable tools, and locally stored credentials, then returning plain-language findings.
    3
    Apache 2.0

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: one generates a read-only SQL query, the other explains the resulting JSON output. The descriptions explicitly describe a sequential handoff, leaving no realistic chance of misselection.

Naming Consistency5/5

Both names follow the same rls_check_<action> snake_case pattern, with query and explain as clear action suffixes. The convention is fully consistent across the set.

Tool Count4/5

Two tools is on the thin side generally, but for this narrowly scoped two-step RLS audit workflow each tool earns its place. There is no obvious extra operation that would justify adding more tools.

Completeness5/5

The pair covers the full lifecycle: generate the diagnostic query, run it externally, then explain the pasted result. The query tool states it reads no row data and the explain tool works offline, so there are no apparent dead ends for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues