Quick start
Requires Node.js 20 or newer. From your app's project root:
npx -y [email protected] check
- In a terminal or CI:
npx -y [email protected] check - For coding agents:
npx -y [email protected] --agent-mode
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @viberaven/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add viberaven-mcp -- npx -y @viberaven/mcp@1.9.0Execute em um terminal.
{ "mcpServers": { "viberaven-mcp": { "command": "npx", "args": [ "-y", "@viberaven/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Requires Node.js 20 or newer. From your app's project root:
npx -y [email protected] check
npx -y [email protected] checknpx -y [email protected] --agent-modeMCP server for VibeRaven: lets Claude Code, Cursor and Codex run the Supabase RLS and security check on an AI-built Vercel + Supabase app and read the findings.
npx.cmd if npx is blocked by the execution policy.It reads supabase/migrations, your client and server code, package.json and .env.example. It does not connect to your Supabase project or send requests to your app. It exits 1 when it finds a blocker, so it also works as a CI step.
Two other Security Advisor lints come up often in the same apps. VibeRaven has no rule for them yet, and the guides explain the fix:
security_definer_view: what it means and how to fix itfunction_search_path_mutable: what it means and how to fix itFor a before-and-after run on one migration, see the missing-RLS example.
From viberaven check 1.6.12 on a synthetic Next.js + Supabase app with one of each gap (project path shortened):
viberaven check · ~/my-app
🔴 No RLS policy proof in migrations (rls_disabled)
1 public table without row level security: public.profiles (supabase/migrations/20260301000000_init.sql:1). The Data API does not enforce row restrictions for roles and operations allowed by the table's grants. Verify those grants to determine who can read or change rows.
🔴 A policy lets anyone write every row (rls_policy_allows_all_write)
Policy "orders are editable" on public.orders (supabase/migrations/20260301000000_init.sql:13) lets anyone, signed in or not, update every row, to any values: using (true).
🔴 Service role key used in client code (service_role_key_in_client_code)
app/admin/page.tsx:4: creates a Supabase client with the service role key. This file ships to the browser, and the service role key skips RLS entirely. Move the call behind a server route or edge function and rotate the key.
🟡 Supabase connection is not using the pooler port (pooler_port_mismatch)
Found direct 5432 DATABASE_URL/POSTGRES_URL evidence. Vercel/serverless deployments should prefer Supabase transaction pooler port 6543.
🟡 Security definer function callable by the Data API roles (security_definer_function_executable)
public.grant_credits(uuid, integer) at supabase/migrations/20260301000000_init.sql:15 is security definer, so it runs with its owner's rights and RLS does not limit what it touches. No migration revokes EXECUTE from public, anon, authenticated, so anyone holding the anon key can call it at /rest/v1/rpc/grant_credits. If only the server calls it, add: revoke execute on function public.grant_credits(uuid, integer) from public, anon, authenticated; Fix: revoke execute on function public.grant_credits(uuid, integer) from public, anon, authenticated;
🟡 Stripe webhook does not verify the signature (unverified_stripe_webhook)
1 Stripe webhook handler without signature verification over the raw body: app/api/stripe/webhook/route.ts (no signature check (constructEvent), no stripe-signature header, no raw body). Anyone who finds the URL can post a fake event, for example a paid checkout.
🟡 Env vars used in code but missing from .env.example (env_var_drift)
Code reads 1 environment variable that .env.example does not document (NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY). Fresh clones, CI, and the production deploy can silently run without them.
🟡 Database queries with no row limit (unbounded_query)
1 file run Supabase selects or Prisma findMany with no .limit()/.range()/take bound (app\admin\page.tsx). These work with 50 test rows and melt with 50,000 production rows.
⚪ No error monitoring detected (missing_monitoring)
No Sentry/PostHog (or similar) instrumentation was found. Production errors will only surface when users complain.
Verdict: ❌ 3 blockers, 5 warnings · score 5
Fix: viberaven fix · Details: ~/my-app\.viberaven\agent-tasklist.md
Every result also lands in .viberaven/ as markdown and JSON (agent-tasklist.md, gate-result.json, context-map.json), so a coding agent and your git history can read it.
Use it:
It is not the right tool when:
These tools answer different questions, and most launches need more than one of them.
We ran the check on the Supabase migrations of 512 public Lovable repos. From the write-up:
In a static read of 512 public Lovable projects on GitHub with a supabase/migrations folder (October 2026), 47.3% (242) define at least one security definer function in the public schema that a signed-out caller with the anon key can run at /rest/v1/rpc.
The post has the method, the limits and the fix. An earlier post covers RLS policies in the same 512 apps.
npx -y [email protected] fix # list gaps with safe automatic recipes
npx -y [email protected] fix --gap <id> --dry-run # preview one recipe
npx -y [email protected] fix --gap <id> # apply it
npx -y [email protected] audit --vercel-supabase # RLS in migrations, pooler port, service_role key
npx -y [email protected] --strict # the verdict as an exit code for CI (exit 1 on not_clear; warnings exit 0)
The rls_disabled recipe adds a migration that enables RLS without policies, so browser reads return no rows until you add policies. Agree before applying it, then apply and test it through your database workflow.
Lovable and Bolt push straight to main, so a pull request check alone misses most of their changes. The VibeRaven GitHub Action runs the same check on pull requests and on pushes, in your own runner:
on:
push:
branches: [main]
pull_request:
permissions:
contents: write
pull-requests: write
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
with:
fetch-depth: 0
- uses: ohad6k/viberaven-action@v1
A pull request gets one comment with what the change added or fixed. A push to main gets a commit comment when there is a blocker. It is advice by default; with fail-on-blockers: 'true' the job fails when it finds a blocker, and your branch protection decides what that means for merging. npx -y [email protected] init --github writes a pull-request-only version of this workflow without the Action.
Give coding agents the same context before they patch the repo:
npx -y [email protected] init --agents all --dry-run # preview
npx -y [email protected] init --agents all
npx -y [email protected] doctor --agents
This installs bounded rules (...) into:
AGENTS.md, CLAUDE.md, GEMINI.md.cursor/rules/viberaven-core.mdc (plus scoped Supabase, deploy, and payments rules).github/copilot-instructions.md.viberaven/agent-context.md, .viberaven/mission-map.mdThe rules say when a pass helps (an AI-built app on Vercel + Supabase, before launch or handoff, or after a migration or policy change) and teach the loop: check, read .viberaven/, fix one gap, then check again once per batch of fixes. They are advice, not a gate: the user decides when to ship.
Six skills.sh skills route agents through architecture questions, version evidence, and launch proof:
npx -y [email protected] add ohad6k/VibeRaven --skill viberaven
See agent-skills/ for the full pack.
This repo also works as an agent plugin: plugin.yaml, .claude-plugin/, .codex-plugin/, and gemini-extension.json expose the six skills plus /viberaven-work, /viberaven-help, /viberaven-production-context, and /viberaven-launch commands to Claude Code, Codex, and Gemini CLI.
For a smaller install, plugins/viberaven is a standalone plugin for Claude Code and Cursor: one skill that says when a pre-launch pass fits a Vercel + Supabase app, plus a version-pinned MCP server. Its manifests specify the package version; the plugin release is separate from the quick start above.
VibeRaven is listed in the MCP registry for agents that prefer tools over terminal commands:
{ "viberaven": { "command": "npx", "args": ["-y", "@viberaven/[email protected]"] } }
Key tools: viberaven_check_readiness (runs the local check), viberaven_heal_apply, viberaven_verify, viberaven_audit, viberaven_gate_result, and viberaven_validate_npm_package (run it before adding npm dependencies).
npx -y [email protected] with no command opens the Studio: a local page where your own coding agent (Claude Code, Codex or Gemini CLI) makes a change in your folder, and you see the steps, your checks, the running app and the diff, with Undo one click away.
The same workflow, fully local, with no account:
npx -y [email protected] in its folder. The Studio opens in your browser.On Windows PowerShell, use npx.cmd if execution policy blocks npx.
The Studio also runs on viberaven.dev: sign in with Google, bring your repo, and connect your computer once. Your agent still works on your computer. The site includes 2 free changes, then Pro for 300 changes a month. Both need a coding agent you are signed in to; its own account and limits apply.
.viberaven/ as plain files that your agent and your git history can read.Contributions are welcome, and most of them need no private source access:
MIT. Current public release: [email protected].
Built by Ohad Krispin (github.com/ohad6k).
If VibeRaven helps you ship, star the repo so other AI app builders can find it. Use Watch → Custom → Releases for release notifications.
VibeRaven public repo is the agent discovery and installation surface. Product source code and service internals live in a private repository.
MCP server for VibeRaven: lets Claude Code, Cursor and Codex run the Supabase RLS and security check on an AI-built Vercel + Supabase app and read the findings.
{ "mcpServers": { "viberaven-mcp": { "command": "npx", "args": [ "-y", "@viberaven/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@viberaven/mcp roda localmente via stdio.
Última verificação: 2026-11-15. MCP server for VibeRaven: lets Claude Code, Cursor and Codex run the Supabase RLS and security check on an AI-built Vercel + Supabase app and read the findings.