VibeScale
Server Details
Pre-launch checks for AI-built apps: leaked keys, Supabase RLS gaps, browser-exposed env vars.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Score is being calculated.
Available Tools
3 toolscheck_env_exposureCheck which environment variables reach the browserRead-onlyIdempotentInspect
Takes environment variable NAMES (never values) and says, for each one, whether the build tool ships it to every visitor (VITE_, NEXT_PUBLIC_, EXPO_PUBLIC_, REACT_APP_, PUBLIC_, GATSBY_, NUXT_PUBLIC_) and whether its name looks like a server secret that must not be there. Use when someone asks whether their .env or API keys are exposed in a Lovable, Bolt, Vite, Next.js or Expo app. Send names only; if a value is included it is dropped and not stored. Explanations are in Hebrew.
Inputs: names (required).
lint_supabase_rlsCheck Supabase SQL for row level security gapsRead-onlyIdempotentInspect
Reads Supabase SQL (migrations or a schema dump) as text and lists tables in exposed schemas without row level security, RLS with no policy, policies that allow everything or read user_metadata, policies without a role, write grants to anon, SECURITY DEFINER functions and views, new tables without a grant, and public storage buckets, each with SQL that fixes it. Use when someone asks whether their Supabase database is locked down, or before launching an app that uses Supabase. The SQL is never executed or stored; policy logic (who should see what) is not judged. Findings are in Hebrew.
Inputs: sql (required).
scan_app_launch_readinessScan a live web app for leaked keys and missing protectionsRead-onlyIdempotentInspect
Reads one public web app the way a browser does (its HTML, the same-site scripts it loads and any source maps they point to) and reports what any visitor can already see: server secret keys shipped to the browser (Supabase service_role, OpenAI, Anthropic, Stripe, AWS, GitHub, SendGrid, Resend; shown masked), a published source map, no HTTPS, and missing Content-Security-Policy, HSTS or frame protection. Use when someone built an app with Lovable, Base44, Bolt, Cursor, Replit or similar and asks whether it is safe to launch or whether a key leaked. It does not sign in, guess paths or query the app's database. Findings are in Hebrew.
Inputs: url (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Security scans for AI-built apps: leaked keys, open Supabase RLS, vulnerable packages, live sites.
Security checks for AI-built apps (Lovable, Supabase, Bolt): RLS, headers, monitoring, fixes.
Security checks for apps built with AI: leaked keys, open routes, database rules, each with a fix.
Free passive security scan for AI-built apps: leaked API keys, public .env files, security headers
Related MCP Servers
- AlicenseAqualityBmaintenanceScan a deployed site for an exposed Supabase service_role key and audit Row Level Security from your AI coding agent.246 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides pre-deploy AI-assisted security and readiness checks for AI-built apps, including scanning for secrets, auth gaps, and payment safety.5MIT
- AlicenseNot gradedqualityFmaintenancePredeploy security scanner for AI-generated code. 80+ vulnerability patterns across secrets, auth, injection, config, Supabase, and logging. Runs locally, code never leaves your machine. Optional x402 witnessed attestation.193 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables 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.5MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.