VIBERAVENMCP

The production layer
for AI‑built apps.

Checks across Supabase, Vercel and Stripe, and a free, open-source engine that races every rule in your database on real PostgreSQL, in your chat or on your machine.

https://viberaven.dev/mcpConnect VibeRaven

Paste the link into ChatGPT, Claude, Codex, Cursor or Lovable. See how

Run it locally
npx -y viberaven race --example
ChatGPT VibeRaven
0007_bookings.sql

Can two users book the last seat? Here is my migration.

Used VibeRaven

VibeRavenrace_two_users24 of 60 orders broke

Both bookings committed.

Rule: at most 2 bookings per event. The event ended with 3.

read committed12/20
repeatable read12/20
serializable0/20
Order 001101✓ Replay byte-identical

Both requests counted 1 booking before either committed, so both inserted. Lock the event row first with select … for update, then count. Fix, run again, and replay order 001101 to confirm.

Results from the bundled example, recorded with VibeRaven 1.10.0.

What VibeRaven does

Find the bugs your users would find first.

The engine

Two users at once

Real PostgreSQL sessions run your rule in every order and replay the one that broke.

How the engine works →
Checks

Across your providers

RLS, keys, webhooks and env, read from the repo before launch and after a change.

Set up in a minute

Connect VibeRaven to your agent

Pick your agent and paste the link. No API key.

Chat apps
For developers

Connect ChatGPT

Custom apps need a plan and workspace that allow them.

  1. Turn on Developer modeSettingsAppsAdvanced
  2. Create an app and paste the link
    https://viberaven.dev/mcp
  3. In a new chat, pick VibeRaven from the + menu.

✓ You’re connected. Try: “Can two users book the last seat?”

In your repo

Check, race, fix.

The same tests run locally from your app folder.

  1. Check

    Find what is risky before launch: RLS, keys, webhooks.

    npx -y viberaven check
  2. Race

    Write viberaven.race.json for your rule, then race it. Node 24+.

    npx -y viberaven race
  3. Fix, run again, replay

    Replay the reported order to confirm the fix holds.

    • exit 0held
    • exit 1broken
    • exit 2incomplete
122/124PostgreSQL isolation specs
1,500/1,500hidden real-app interleavings
80/80byte-equal replays
0leaks in 60 isolation cases