Security checks for Next.js + Supabase apps: code scan, read-only live DB check, fix confirmation.
Connect Remote server
claude mcp add --transport http guardlayer https://www.guardlayer.io/api/mcp
{
"mcpServers": {
"guardlayer": {
"url": "https://www.guardlayer.io/api/mcp"
}
}
}
{
"servers": {
"guardlayer": {
"type": "http",
"url": "https://www.guardlayer.io/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://www.guardlayer.io/api/mcp
Tools 3 found in our last check
scan_filesStatic security scan of a Next.js + Supabase codebase: secrets in code or public env vars (NEXT_PUBLIC_, VITE_), service role keys in client code, RLS off or open policies in supabase/migrations, unauthenticated API routes, Server Actions and Edge Functions, unsafe redirects and…
get_supabase_snapshot_sqlReturns the read-only SQL for the live Supabase check and how to run it. It reads only catalog metadata (table and column names, RLS flags, policies, grants, triggers, SECURITY DEFINER functions, bucket settings), never table rows, and returns one JSON value.
check_supabase_snapshotChecks the JSON from get_supabase_snapshot_sql: tables anyone can read, RLS off, policies that only check for a signed-in user (public in practice when sign-ups are open), users who can update their own role or plan columns, exposed SECURITY DEFINER functions, public buckets. Pa…
Details
| Endpoint | https://www.guardlayer.io/api/mcp (Streamable HTTP) |
| First published | 10 Nov 2026 |
| Last updated | 10 Nov 2026 |
| Registry name | io.github.solvionholdings/guardlayer |
More databases servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
