Skip to main content
Glama

Server Details

Check Supabase migrations for RLS and grant gaps; fixes for Supabase, Vercel, Stripe errors.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
ohad6k/VibeRaven
GitHub Stars
1
ChatGPT
VibeRaven
Claude
VibeRaven Guides

TDQS

A4.3/5.0

Scored across 7 tools

Disambiguation4/5

The two scan tools (check_github_repo vs check_supabase_migrations) apply the same rule set and differ only in input source, which is spelled out in the descriptions but is still the most likely misselection point. The guidance tools are separated by explicit axes—setup (provider_playbook), dated changes (recent_provider_changes), error lookup (search_guides), pre-launch (launch_checklist)—and each description names the sibling to use instead.

Naming Consistency4/5

All names are snake_case and readable, with a mostly verb-first pattern (check_*, explain_finding, search_guides). launch_checklist, provider_playbook, and recent_provider_changes are noun phrases rather than verb_noun, a minor deviation but not confusing.

Tool Count5/5

Seven tools is well-scoped for a Supabase/Vercel security-review assistant: two scanners, one finding explainer, and four guidance lookups. No redundant or filler tools; each maps to a distinct step in the review workflow.

Completeness4/5

The surface covers scan (pasted SQL or GitHub repo), explain a finding, and look up guides, playbooks, and dated changes—a coherent end-to-end advisory loop. Gaps: no live-database or private-repo check (acknowledged as planned), no tool to enumerate all finding ids/providers, and provider_playbook only ships a Supabase pack while other tools list eight providers.

Available Tools

7 tools
check_github_repoCheck a public GitHub repo for Supabase RLS gapsA
Read-onlyIdempotent
Inspect

check_github_repo({"repo":"owner/name"}) Check the Supabase migrations of a public GitHub repository for missing RLS or policies, policies that let anyone read or write every row, exposed security definer functions and Data API grant gaps. Use it when the user names or links their app repo (Lovable, Bolt, v0 and Cursor apps synced to GitHub) and has no terminal. Reads supabase/migrations/*.sql at one commit with the VibeRaven 1.8.0 SQL rules and returns finding id, severity, file, line, a link to that line, a fix and a guide link. Limits: public repositories only, up to 50 files/200 KB; cannot see the live database or private repos, does not run SQL, and does not store files.

Inputs: repo (required), ref. Returns: scope, counts, skipped, findings, +7 more

check_supabase_migrationsCheck Supabase migrations for RLS and grant gapsA
Read-onlyIdempotent
Inspect

check_supabase_migrations({"sql":"create table public.notes (id bigint);"}) Use when reviewing Supabase migration changes for missing RLS or policies, unrestricted read/write policies, exposed security definer functions and Data API grant gaps. Pass file contents: sql contains one migration's SQL text; files contains path and content for each file. Runs the VibeRaven 1.8.0 SQL rules and returns finding id, severity, file, line, a suggested fix and a guide link. For missing Data API grants, include the migration revoking default privileges or supabase/config.toml, plus browser files using supabase.from(...) (a "use client" file, or src files with package.json for Vite). Limits: supplied text only, up to 200 KB/50 files; cannot access your repository or database, does not execute SQL, and does not store or log file contents.

Inputs: sql, files. Returns: scope, counts, skipped, findings, +6 more

explain_findingExplain a VibeRaven findingA
Read-onlyIdempotent
Inspect

explain_finding({"gap_id":"rls_disabled"}) Use after a check returns a finding id, such as rls_disabled or env_var_drift, to understand and fix that VibeRaven 1.8.0 finding. Returns detection scope, impact, fix guidance and coverage limits quoted from viberaven.dev with source links. Unknown ids return found: false and known ids. For a raw error without a finding id, use search_guides. Limits: explains published rules only; does not read your repo, database or Vercel project.

Inputs: gap_id (required). Returns: found, gap_id, detects, named_on, +6 more

launch_checklistGet a launch checklistA
Read-onlyIdempotent
Inspect

launch_checklist({"stack":"nextjs-supabase-vercel"}) Use for a broad pre-launch review of a Lovable + Supabase app or a Next.js + Supabase app on Vercel. For a specific failing request, use search_guides. Returns a published manual checklist with sources and an optional local repo check (npx -y viberaven@1.8.0 check). Limits: checklist guidance only; does not run checks or verify dashboards, code or launch readiness.

Inputs: stack (required). Returns: url, items, stack, title, +4 more

provider_playbookGet a provider playbookA
Read-onlyIdempotent
Inspect

provider_playbook({"provider":"supabase","topic":"grants"}) Use before implementing a feature that touches a provider, when setup or integration rules are needed. Returns versioned setup guidance, gotchas, dated changes, integration seams, existing repo checks and planned live checks with official sources. Available packs: supabase. Pass topic to return matching items; for a specific error use search_guides, for dated changes use recent_provider_changes. Limits: guidance only; does not connect to providers, read your project, run checks or verify that a feature works.

Inputs: provider (required), topic. Returns: pack, topic, nextStep, packHash, +3 more

recent_provider_changesCheck recent provider changesA
Read-onlyIdempotent
Inspect

recent_provider_changes({"provider":"supabase","query":"42501","limit":5}) Use when a provider update may explain changed behavior, or a deployment needs review against dated provider changes. Returns candidate changes, documented errors or symptoms, fixes, date meanings and official supporting sources. Filter by provider or redacted error keywords. For general troubleshooting use search_guides; for setup use provider_playbook. Available providers: anthropic, clerk, lovable, nextjs, openai, railway, stripe, supabase, vercel. Limits: guidance only; does not read your repo, connect to providers, run fixes or verify rollout, deployment or live behavior.

Inputs: limit, query, provider. Returns: limits, entries, nextStep, packHash, +6 more

search_guidesSearch VibeRaven launch guidesA
Read-onlyIdempotent
Inspect

search_guides({"query":"supabase tables missing rls"}) Find troubleshooting steps for exact errors in Supabase RLS, Realtime and auth; Clerk middleware and sessions; Better Auth origins and OAuth callbacks; Vercel environment variables and deployments; Stripe webhooks; or Storybook environment variables and 404s. Search published viberaven.dev guides by keywords or error text; returns up to 5 titles, URLs and short answers. Also covers Lovable + Supabase launch checks and client handoff. No match returns an empty list. Limits: searches the indexed published guides only; does not browse the web or read your project.

Inputs: query (required). Returns: results, nextStep

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets coding agents ask whether a Supabase migration is safe to merge: it replays the base branch and working tree into throwaway databases, reports only the findings the change introduces, and proves RLS leaks by querying as anon. Tools are read-only and take profile names instead of connection strings.
      10 npm
      MIT
    • 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
      B
      quality
      B
      maintenance
      Read-only Supabase Row Level Security review. Analyzes an exported catalog query (no keys needed) for RLS turned off, policies that are just true, anon-callable SECURITY DEFINER functions, views exposing auth.users, public Storage buckets and more, and explains each rule.
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.