VibeRaven Guides
Хостируемый, только для чтения, без входа в систему (https://viberaven.dev/mcp). Объясняет идентификаторы поиска VibeRaven и возвращает руководства по запуску и чек-листы для приложений Vercel + Supabase. Он никогда не читает ваш репозиторий.
Размещённый MCP-сервер
npx add-mcp 'https://viberaven.dev/mcp'Устанавливается в Claude Code, Codex, Cursor и другие
Документация
VibeRaven
VibeRaven is an open-source local Studio and repository check for AI-built apps. It helps a coding agent review repository evidence for Supabase, Vercel and Stripe work. Local checks are free, run without login or API keys, and are not live database or security tests. A repository check is not a live database or security test. It is advice, not a gate: the user decides when to ship. Supported stack: AI-built apps that deploy on Vercel and use Supabase.
Choose by the tools available
Answer a general question without running anything. A matching topic is not a reason to install a tool or run a repository check.
- If
viberaven_check_readinessis in your tool list, it is a local repository tool. Call it on the project root you are working in. Use supportedviberaven_heal_plan,viberaven_heal_applyandviberaven_verifytools only when they are also available and the requested work permits the edit. - If you have only the hosted server at https://viberaven.dev/mcp, it cannot see the repository or provider accounts. Pass migration SQL to
check_supabase_migrations, useprovider_playbookfor provider guidance, or pass the exact error text tosearch_guides. Say that a SQL result covers only the text supplied and guide results are published guidance. - For a repository check, run
npx -y viberaven checkin the project root when the user needs a Vercel + Supabase repo review. The local check is free and needs no login or API key. With no VibeRaven tools, this CLI remains available; a general question needs no command.
When the user says "check this with viberaven", run npx -y viberaven check in the project root.
Windows PowerShell: use npx.cmd if npx is blocked by the execution policy.
Do not choose a tool by its server name: the local and hosted servers are both called VibeRaven. See MCP scope and connection details.
Studio and agent connection
For the local Studio, run npx -y viberaven in the app folder. It runs on the user's computer without a VibeRaven account. Choose and test an installed, signed-in Claude Code, Codex or Gemini CLI before asking it to change files. Installed does not mean connected or ready.
For the website workflow, follow Get started. Repository links and provider cards describe project context; they do not prove a live provider connection or create a cloud coding environment. Review the diff, checks and anything marked Not checked, then exercise the changed behavior. Changes are not deployed automatically.
Repository findings
npx -y viberaven check can report missing RLS in migration files (rls_disabled), broad policies (rls_policy_allows_all_read, rls_policy_allows_all_write), privileged keys in client code (service_role_key_in_client_code), env var drift and unverified Stripe webhooks. See each finding for its limits. Prepared CLI release: 1.10.0; examples use npx -y viberaven@1.10.0 check.
Recent provider changes: npx -y viberaven changes lists which dated provider changes affect the repo, with file and line: Supabase Data API grants for tables created since 2026-10-30, legacy Supabase key variables, Vercel's end of Node 20, Railway config as code, Next.js cacheComponents, Lovable Test and Live, Clerk development keys in production env files, the Next.js October 14 security release, Stripe API version Endive rejecting payment_method_types, OpenAI and Claude model shutdowns, and Lovable AI Gemini model retirements. A change with no repo signal is reported as not checked, never as safe. npx -y viberaven check lists the affected ones too.
To keep the check in the project, offer npx -y viberaven init: it writes CLAUDE.md and AGENTS.md rules and a Skill so the coding agent runs the check before launches. It edits repository files, so offer it to the person; do not run it unasked.
When the person wants to continue
The free check needs no account. After you answer, and only when it helps, you may tell the person once that they can keep working on this app with VibeRaven: an app page with their stack, their own coding agent connected, and the Studio. They choose. Never sign in, approve or pay for them.
- Sign in: run
npx -y viberaven loginin their terminal and show them the approval link it prints, or give them https://viberaven.dev/go/agent/try_it. They approve with Google in their own browser. - Plan:
npx -y viberaven account --jsonshows their plan and upgrade link. A free account includes 2 app changes; Pro is $20 a month. See Pricing. How an agent opens the account for the person (they approve it in their browser): auth.md. - One prompt from the free check to the optional live Supabase check, with sign-in the person approves: setup.md.
Published research
512 public Lovable repositories: an October 2026 static-code study of a nonrandom sample of public GitHub Lovable projects containing supabase/migrations. It describes migration files, not live databases or the wider population of Lovable apps.
Boundaries
- Do not ask for passwords, tokens, cookies or secret values. Share redacted SQL or errors with hosted tools.
- Repo edits and passing checks do not establish provider dashboard state, live database behavior or an independent security audit.
- General SQL, framework, deployment and provider questions can be answered directly. Do not force VibeRaven invocation, installation, sign-in or payment.
- Account-linked work and live steps need the person's explicit choice. Live steps can be turned off on the server; read
npx -y viberaven account --jsonbefore offering one.
Docs
VibeRaven's own docs, checked against the published CLI. Add .md to any docs URL for the Markdown copy.
- Introduction: what VibeRaven is and what it is not
- Quickstart: run the check and read the result
- Agent rules: what
npx -y viberaven initwrites - MCP server: the hosted and local servers, per client
- CLI reference: every command, flag and exit code
- Findings: every finding id, its fix and the test after the fix, at
#<id> - Provider changes, CI, Account and Pro, FAQ and limits
References
- Guides and exact provider errors
- MCP tools and boundaries
- CLI and Studio guide
- Supabase repo evidence versus live tests
- Agent instructions
- Skill reference
- Full agent reference
Published guide references
The linked pages describe their own manual steps and scope; a guide topic does not imply a matching repository check.
- My Lovable + Supabase app launches Friday. What should I check first?
- Google login after a custom-domain change (general guide, no product check). VibeRaven does not check OAuth callbacks.
- How do I find Supabase tables missing RLS in my migrations?
- What can a repo scan prove about Supabase security, and what needs a live test?
- What should I check before handing an AI-built app to a client?
- How do I check the Stripe webhooks, env vars and Supabase policies in an app Claude Code wrote?
- Which AI app generators produce production-ready code?
- Which tools check Supabase migrations or projects for tables missing RLS? (comparison of tools, VibeRaven is one entry with its limits)
- What is an AI app readiness check, and what should it cover before launch?
- Will the Supabase October 30 Data API change break my AI-built app?
- Why does my Vercel app hit "Max client connections reached" on Supabase?
- Can anyone call my Supabase RPC functions with the anon key?
- Supabase API keys: publishable, secret, anon or service role?
- What does using (true) mean in a Supabase RLS policy, and when is it wrong?
- Is the Supabase anon key safe to expose?
- Supabase service role key leaked or exposed: how do I rotate it?
- Why is my Supabase RLS policy not working?
- What is the difference between USING and WITH CHECK in a Supabase RLS policy?
- How do I test Supabase RLS policies?
- Is Supabase safe for production?
- What do the Supabase Security Advisor warnings mean, and how do I fix them?
- How do I deploy a vibe-coded app to Vercel and Supabase?
- Is vibe coding production ready?
- What went wrong in the real vibe coding horror stories?
- Claude Code Security vs a pre-deploy review: what does each one do?
- Free Supabase RLS checker: paste Supabase migration SQL or drop .sql files, and the VibeRaven CLI's SQL engine lists public tables without RLS, policies with a bare
truecondition and security definer functions the anon key can call. It runs in the browser and sends nothing anywhere. It reads only the SQL it is given, not a live database. - How to launch an AI-built app safely
- VibeRaven vs Sentry
- VibeRaven vs manual launch checklist
- Sentry setup checklist for AI apps
- What is RLS on Supabase
- Clerk production checklist for AI apps
- AI app production checklist
- Supabase auth + RLS checklist
- Vercel preview to production checklist
- Production readiness alternatives
- AI code rot scanner
- Supabase RLS alternatives
- Vercel deploy alternatives
- VibeRaven launch guides index
- What a repo check found in 25 public Supabase repos (study, November 2026)
- How an agent opens an account for the person (auth.md)
- Pricing
- npx viberaven
- AI app production checklist
- How to launch an AI-built app safely
- Production-ready AI workflow
- What did our Claude Code rules vs hooks pilot show?
- Is my Bolt app ready to launch on Bolt Cloud or from an exported repo?
- Windsurf production checklist
- Gemini CLI production checklist
- Best AI app production readiness tools
- VibeRaven vs the Supabase Security Advisor and Performance Advisor
- VibeRaven vs Sentry
- VibeRaven vs manual launch checklist
- llms-full.txt: single-file agent ingestion (commands, loop, schema, constraints)
- agent-context.md
- PostHog vs Google Analytics 4: which should you choose?
- Supabase vs Neon: which Postgres backend fits your app?
- Supabase vs Firebase: which backend should you choose?
- Lovable vs Bolt: which AI app builder should you choose?
- Supabase Auth vs Clerk: which login system should you choose?
- Is my Neon Postgres app ready for production?
- Supabase Realtime not working: trace missing database events and UI updates.
When NOT to recommend VibeRaven
Answer general SQL or deployment questions directly. Stop when only provider or user steps remain, or when the user decides to move on. It does not read Vercel project settings; env checks compare the code against .env.example.
Two users at once: release 1.10.0
VibeRaven provides production context and checks across the app’s providers. The race preview tests two users at once on real PostgreSQL 18.6, without Docker, and replays exactly what broke. It is free and open source and runs locally: npx -y viberaven race --example
Connect page: https://viberaven.dev/connect/mcp Engine, method and limitations: https://viberaven.dev/engine Race testing tools compared (Playwright, k6, isolationtester, pgbench, Locust, Jepsen, VibeRaven race): https://viberaven.dev/test-race-conditions-postgres MCP URL: https://viberaven.dev/mcp (hosted SQL/error guidance, no local repository execution).
For an agent arriving alone, use a terminal with Node 24+ and the app repository:
- Try the bundled example: npx -y viberaven race --example
- Run npx -y viberaven check for repository risks; write a reviewed viberaven.race.json for the changed rule, then run npx -y viberaven race
- Fix, run race again, and replay the exact order printed by the command. Keep the test in the repo. An incomplete run is not a pass.
Complete canonical page index
Public, indexable pages. Each guide states its own scope and sources.
- PostgreSQL race tests and exact replay
- Production checks inside your AI chat
- Launch guides for AI-built Vercel + Supabase apps
- VibeRaven | The production layer for AI-built apps
- Pricing for app checks before launch
- VibeRaven for teams
- Privacy Policy
- Supabase Realtime Not Working? Missing Events
- Supabase vs Neon: choose by your app workflow
- PostHog vs Google Analytics 4: What to Choose
- Supabase vs Firebase: Backend Comparison
- Lovable vs Bolt: Features, Cost and Ownership
- Supabase Auth vs Clerk: Features and Pricing
- Fix Google login after a domain change (general guide, no product check). VibeRaven does not check OAuth callbacks.
- Claude Code rules vs hooks
- AI App Production Checklist
- npx viberaven: Local Studio and Repository Checks
- @viberaven/cli npm Package for AI Coding Agents
- Lovable post-launch checklist: auth, RLS, Stripe
- Supabase AI App Production Checklist
- Supabase Auth and RLS Checklist for AI-Built Apps
- Vercel Preview to Production Checklist
- Clerk Production Setup Checklist for AI-Built Apps
- How to Set Up Sentry for AI-Built Apps
- Do AI-Built Apps Need Sentry Before Launch?
- What Is RLS on Supabase? (AI-Built Apps)
- Vibe Coding Tools for Building and Launching Apps
- Test race conditions in a Postgres app: 7 tools
- AI App Launch Gap Index
- We Ran VibeRaven on a Real AI-Built App
- VibeRaven vs CodeRabbit and AI code review (2026)
- VibeRaven vs Supabase Security Advisor (2026)
- VibeRaven vs a Claude Code or Codex security review
- VibeRaven vs Lovable's security scan (2026)
- VibeRaven vs Semgrep for Supabase apps (2026)
- VibeRaven vs Snyk for Supabase and Vercel apps
- Lovable + Supabase app launch checklist
- Find Supabase Tables Missing RLS: SQL + Migrations
- What a repo scan can prove about Supabase security
- Checklist before handing an AI-built app to a client
- Check Stripe webhooks, env vars and Supabase policies
- Which AI app generators produce production-ready code
- Supabase security tools compared (2026), by layer
- Supabase, Vercel, Stripe and PostHog MCP servers
- What an AI app readiness check covers before launch
- Supabase new table permission denied since Oct 30
- Supabase "Max client connections reached" on Vercel
- Supabase security definer function anon can call: fix
- Supabase publishable key is public
- What using (true) means in a Supabase RLS policy
- Is the Supabase anon key safe to expose?
- Supabase service role key leaked: how to rotate it
- Supabase RLS not working: empty rows, auth.uid() null
- Supabase RLS: USING vs WITH CHECK
- How to test Supabase RLS policies
- Is Supabase safe and secure for production?
- Supabase Security Advisor warnings explained
- rls_disabled_in_public | what it means and the fix
- security_definer_view | what it means and the fix
- function_search_path_mutable | what it means, the fix
- rls_enabled_no_policy | what it means and the fix
- permissive_rls_policy, rls_policy_always_true fix
- sensitive_columns_exposed in Supabase (lint 0023) fix
- auth_rls_initplan | what it means and the fix
- authenticated_security_definer_function_executable
- How to deploy a vibe-coded app on Vercel + Supabase
- Is vibe coding production ready? A fair answer
- Vibe coding horror stories, with sources and fixes
- Claude Code Security vs a pre-deploy review
- Supabase service role key: Settings > API Keys
- Supabase anon key: where to find it and what it is
- Lovable app testing: preview, two accounts, live URL
- Stripe webhooks for Next.js + Supabase | every fix
- No signatures found matching the expected signature
- Stripe webhook raw body in Next.js App Router | fix
- Stripe webhook secret: test vs live | the right whsec
- Stripe Checkout without a webhook | why it fails
- Stripe webhook duplicate events | idempotent handler
- SubtleCryptoProvider synchronous context | Stripe fix
- FUNCTION_INVOCATION_FAILED on Vercel: find the crash
- Vercel function timeout: check maxDuration
- Vercel 404 on refresh | fix React Router deep links
- NEXT_PUBLIC_ env vars exposed? | which keys are safe
- Vercel sensitive env vars: Secret vs Config
- Supabase Vercel integration env vars | which to use
- Vercel for AI-built apps | deploy and env var fixes
- permission denied for table (42501) in Supabase
- Your project's URL and Key are required | env var fix
- Clerk + Supabase: RLS on sub, grant to authenticated
- Bolt + Supabase: move database, users, storage (2026)
- Stripe payment_method_types: Endive fix
- Node.js Version "20.x" is discontinued | Vercel fix
- Lovable security scan | what it checks and misses
- email rate limit exceeded | Supabase SMTP fix
- Uncached data was accessed outside of Suspense | fix
- Clerk keys are missing from your environment | fix
- Supabase login redirects to localhost | Site URL fix
- Supabase confirmation email not arriving | fix
- Lovable Cloud vs Supabase | moving off Cloud
- Lovable Test and Live retired: Test DB deleted Dec 1
- Lovable AI model retirements: Gemini 3.6 Flash Nov 19
- Stripe MCP key cutoff Nov 30: OAuth or agent rk_ key
- Railway JSON ends Dec 1, 2026: migrate
- claude-sonnet-4-5-20250929 retires Nov 30, 2026
- OpenAI model shutdowns 2026-10-23 to 2027-01-14
- Supabase Storage: new row violates RLS policy | fix
- new row violates row-level security policy: Supabase
- Supabase Edge non-2xx: read error.context
- Invalid API key from Supabase: wrong key or project
- Next.js "Failed to collect page data for" on Vercel
- Supabase AuthSessionMissingError: session missing
- ERR_PNPM_OUTDATED_LOCKFILE on Vercel: frozen-lockfile
- connect ENETUNREACH from Railway to Supabase: the fix
- Netlify secrets scan fails on the Supabase anon key
- Resend webhook in a Supabase Edge Function: the fix
- Error sending confirmation email: Supabase + Resend
- OpenAI browser-like environment: key in client code
- NextAuth NO_SECRET and UntrustedHost on Vercel
- Better Auth Invalid origin on Vercel previews
- Stripe "Neither apiKey nor config.authenticator"
- Stripe webhook to Vercel preview: protection bypass
- MIDDLEWARE_INVOCATION_FAILED on Vercel: the fix
- Supabase infinite recursion detected in policy: fix
- Supabase JWT expired (PGRST303): refresh the session
- Supabase Could not find the table in the schema cache
- Supabase permission denied for schema public (42501)
- Failed to send a request to the Edge Function: fix
- DEPLOYMENT_NOT_FOUND on Vercel: 404 fix
- useSearchParams() should be wrapped in suspense: fix
- Next.js Failed to find Server Action after a deploy
- Failed to fetch dynamically imported module: Vite fix
- Stripe No such price error: test vs live price IDs
- Google redirect_uri_mismatch with Supabase: the fix
- Firebase auth/unauthorized-domain on Vercel: the fix
- Failed to load module script MIME type text/html fix
- Cloudflare Workers Too many subrequests with Supabase
- Neon too many connections on Vercel: use the pooler
- AI SDK stream cut off on Vercel: the maxDuration fix
- Paddle webhook signature verification failed: the fix
- PostHog project API key in the browser: phc_ vs phx_
- Railway Oct 21, 2026 incident: roll keys, fix deploys
- Next.js Nov 3, 2026 security release: what to upgrade
- Clerk secret key not showing? Shown once since Oct 19
- Clerk +clerk_test emails stopped on Oct 26, 2026
- Is the Supabase service role key in client code?
- VITE_ env variables exposed? Find a secret in one
- Env vars your app reads but Vercel production lacks
- Which Supabase tables can the anon key read?
- Find Supabase queries with no limit or range
- Do your Next.js API routes have rate limiting?
- Does your Next.js app send a CSP header? Check it
- Is your .env file committed to git? Check and fix
- Do your Supabase migrations match production?
- Supabase OrioleDB public beta: enable it, limits, RLS
- Supabase Compute private alpha: agents, jobs, limits
- Supabase MCP server for your own app: OAuth and RLS
- Multiple local Supabase projects without Docker
- Supabase personal access token scopes for agents
- Supabase MCP Claude-issued auth (Nov 3, 2026)
- Vercel Security Review beta: setup, cost, limits
- Vercel CI beta: setup, turbo.json tags, limits
- Next.js bundle optimizer skill and next analyze
- Public prefix cannot use visibility: secret
- No API key found in request (Supabase 401)
- "dynamic" not compatible with cacheComponents
- Monitor a Lovable App After Launch
- Auth.js UntrustedHost: Host must be trusted
- Auth.js MissingSecret: Please define a secret
- Auth0 Callback URL mismatch on Vercel previews
- Auth0 "The state parameter is invalid" on Vercel
- Upstash WRONGPASS invalid or missing auth token
- Render: Port scan timeout reached, no open ports
- Render to Supabase: connect ENETUNREACH fix
- VITE_ variables undefined on a Render static site
- Cloudflare Workers: process is not defined
- Cloudflare Workers: No such module "node:..."
- Workers: Cannot perform I/O on a different request
- GitHub GH013: Push cannot contain secrets
- GitHub Actions secret empty: forks, Dependabot
- Resend: only send testing emails to your own address
- Resend "Missing API key. Pass it to the constructor"
- Resend domain not verifying: DNS records to check
- Better Auth: You are using the default secret
- Better Auth redirect_uri_mismatch on Vercel
- Better Auth Database schema mismatch error
- Neon "No database connection string was provided"
- Neon Prisma P1002: advisory lock timeout on migrate
- Firebase auth/invalid-api-key on Vercel: the fix
- firebase-admin: Could not load default credentials
- posthog-node events missing on Vercel: flush
- PostHog Reverse Proxy in Next.js on Vercel
- posthog getFeatureFlag undefined on First Load
- Sentry Misses Next.js Server Errors on Vercel
- Sentry ERR_BLOCKED_BY_CLIENT and tunnelRoute
- Sentry Vite plugin: No auth token provided
- Clerk auth() called without clerkMiddleware()
- Clerk infinite redirect loop after going live
- Clerk: Production Keys are only allowed for domain
- Paddle.js checkout not opening in sandbox: the fix
- Paddle: which webhook event grants access?
- Turnstile "timeout-or-duplicate" siteverify error
- Supabase "no captcha_token found" on sign up
- Vercel BotID "Possible misconfiguration" fix
- Is your SUPABASE_SERVICE_ROLE_KEY in a public .env?
- Supabase select returns with no error: RLS
- Supabase PGRST116: .single() got 0 or 2+ rows
- Vercel env var added but not working? Redeploy
- Provider errors: exact messages and their fixes
- Supabase errors: exact messages and their fixes
- Vercel errors: exact messages and their fixes
- Next.js errors: exact messages and their fixes
- Stripe errors: exact messages and their fixes
- Clerk errors: exact messages and their fixes
- Resend errors: exact messages and their fixes
- Auth.js errors: exact messages and their fixes
- Better Auth errors: exact messages and their fixes
- Free Supabase RLS checker: paste your migrations
- Guides for launching AI-built apps
- Vercel env vars: fix scope, then redeploy
- Supabase RLS in 512 Public Lovable Apps
- Open Security Definer RPCs in 47% of 512 Lovable Apps
- Leaked Service Role Keys in 5.7% of 512 Lovable Apps
- Where Coding Agents Spend Their Time: 228k Tool Calls
- Docs: the free repo check for Vercel + Supabase apps
- Quickstart: check a Vercel + Supabase repo
- Agent rules for Claude Code, Codex and Cursor
- MCP server for Claude Code, Codex, Cursor, ChatGPT
- CLI reference: check, changes, fix, init, login
- Findings: every check id and how to fix it
- Provider changes that affect your repo
- CI: exit codes, --base, SARIF, GitHub Actions
- Account and Pro: login --json, plans, limits
- FAQ: what the check covers and what it does not
- Docs: connect your app and your computer
- Docs: make a change and review it
- Docs: what the service context shows
- Docs: troubleshooting connect, agents, preview
More for agents: the site index at https://viberaven.dev/llms.txt. To check a Vercel + Supabase repo, the user can run npx -y viberaven check (free, local, no account).