GuardLayer
io.github.solvionholdings/guardlayer · v1.0.1 · MCP 2025-06-18
Security checks for Next.js + Supabase apps: code scan, read-only live DB check, fix confirmation.
Reachability
reachable
checked 2026-11-21 05:41 UTC
Registry status active
Tools pinned 3
8467f908a96a
Tools last changed
unchanged since first capture 2026-11-11
Repo last push 2026-11-11
as of 2026-11-21
GitHub stars 0
as of 2026-11-21
Provenance
Registry namespace io.github.solvionholdings
(GitHub-account verified by the official registry)
Repository
github.com/solvionholdings/guardlayer-plugin
Website
https://www.guardlayer.io/mcp
Remote endpoints
https://www.guardlayer.io/api/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-11 05:30 | first capture | 3 tools pinned |
Pinned tool definitions (3)
| Tool | Description |
|---|---|
| scan_files | Static 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... |
| get_supabase_snapshot_sql | Returns 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... |
| check_supabase_snapshot | Checks 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... |
Get alerted when this changes.
Email the moment io.github.solvionholdings/guardlayer drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/io.github.solvionholdings/guardlayer)
Maintain this server? Add the badge to your README. It links your users to this live status page.