mcpbeat Sign in

VibeRaven MCP Server

not responding

VibeRaven is listed as active in the registry but did not answer our last check. It exposes 4 tools. Last commit 29 Oct 2026.

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

Uptime history 33 days of history · worst day 0%
33 days agonow
0.0%
Uptime 24h
0 of 91 checks
4
Tools
read from the server
77 ms
Response time
average over 24h
61
Stars
last commit 29 Oct 2026

What changed 19

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

25 Oct a tool appeared check_supabase_migrations
9 Oct 2 tool descriptions were rewritten explain_finding, launch_checklist
9 Oct a tool changed version
8 Oct 2 tool descriptions were rewritten explain_finding, launch_checklist
6 Oct 2 tool descriptions were rewritten4 times that day explain_finding, launch_checklist
6 Oct a tool changed version
4 Oct 2 tool descriptions were rewritten4 times that day explain_finding, launch_checklist
4 Oct a tool changed version
2 Oct 2 tool descriptions were rewritten explain_finding, launch_checklist
1 Oct a tool changed version
and 4 more, back to 1 October 2026

VibeRaven does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add viberaven-guides --transport http https://viberaven.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://viberaven.dev/mcp
~/.codex/config.toml
[mcp_servers.viberaven-guides]
url = "https://viberaven.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "viberaven-guides": {
      "url": "https://viberaven.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "viberaven-guides": {
      "type": "http",
      "url": "https://viberaven.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

explain
explain_finding
Use this when the user asks what a VibeRaven finding id means, for example rls_disabled or env_var_drift, or pastes a finding from a VibeRaven 1.6.12 report. Returns what the rule detects in repository files, why it matters, how to fix it and what it does not check, quoted from viberaven.dev with a source link for each part. It does not read the user's repository, database or Vercel project. Known ids: rls_disabled, rls_no_policies, rls_policy_allows_all_read, rls_policy_allows_all_write, security_definer_function_executable, pooler_port_mismatch, service_role_key_in_client_code, env_var_drift. An unknown id returns found: false and the list of known ids.
guides
search_guides
Use this when the user has a launch question about an AI-built app on Vercel + Supabase, such as Supabase RLS, env vars on Vercel, a Stripe webhook after deploy or a client handoff. Searches the launch guides published on viberaven.dev by keyword and returns up to 5 matches, each with its title, URL and the short answer from the page. It only searches those published pages: it does not browse the web or read the user's project. No match returns an empty list.
launch
launch_checklist
Use this when the user wants a manual pre-launch checklist for a Lovable + Supabase app or a Next.js + Supabase app on Vercel. Returns the checklist published on viberaven.dev for that stack with its sources, and the one optional local VibeRaven step (`npx -y [email protected] check`), which is advice, not a gate. The items are manual checks the user does in their dashboards and code; this tool does not run any of them.
supabase
check_supabase_migrations
Use this when the user wants their Supabase migrations checked for RLS gaps before launch, asks whether the Supabase October 30, 2026 Data API grants change will break their tables, or asks whether a security definer function is callable by anon or by signed-in users. Pass the SQL text: sql for one migration, or files with path and content for several, in the repo's file names. It runs the SQL rules of the VibeRaven 1.6.12 CLI and returns each finding with id, severity, file and line in the text passed, a one-line fix and a guide link. Finding ids: rls_disabled (table without RLS), rls_no_policies (RLS on, no policies), rls_policy_allows_all_read and rls_policy_allows_all_write (using (true) or with check (true) for anon, authenticated or public), security_definer_function_executable (EXECUTE not revoked from anon or authenticated), data_api_grant_without_rls (table granted to anon or authenticated with RLS off), data_api_grant_missing (the browser queries a table that has no grant once default grants are off). data_api_grant_missing needs the migration that revokes default privileges or supabase/config.toml, plus the browser files that call supabase.from(...) (a "use client" file, or src files with package.json for a Vite app). It is a static read of the text passed: it does not connect to the database, does not run the SQL and does not see the rest of the repository. Up to 200 KB in 50 files. The text is processed in memory, not stored and not logged.

Endpoints

URLTransportStateLatencyChecked
https://viberaven.dev/mcp streamable-http answering 77 ms 9 min ago

Alternatives to VibeRaven

same job, measured the same way
Securealy
by securealy

Grade a URL as an attacker and a customer would see it; scan a repo; check Supabase, Stripe, Vercel.

144 installs/wk local only
Viberaven
by ohad6k

Checks a Vercel + Supabase repo before deploy: RLS, grants, leaked keys, webhooks. Runs locally.

558 installs/wk local only
Appbase
by cloudcorprecords

Supabase projects, tables, SQL, migrations, and storage from your MCP client.

local only
RetentionCheck
by brianfofficial

Pull churn from Stripe, Postgres, MySQL, or pasted feedback. AI-ranked drivers + fixes.

58 installs/wk local only
SupaForge
by akalsoftware

Find and fix drift between Supabase environments: schema, RLS, roles, auth, storage and more.

498 installs/wk local only
Supabase
by mcp-dir

Your Supabase account in natural language: run SQL, apply migrations, manage tables, storage, edge f

35 tools answering
M
MCP Schema Designer
by vpatser1

Design database schemas from natural language, validate SQL, generate migrations and types

41 installs/wk local only
Ashlr Stack
by ashlrai

Provision and connect third-party dev services (Supabase, Vercel, and more) from your coding agent.

244 installs/wk local only

VibeRaven — questions

Answers built from our own checks of this server.

What can VibeRaven do?
It exposes 4 tools, read directly from the server on our last check. Among them: check_supabase_migrations, explain_finding, launch_checklist, search_guides. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is VibeRaven working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 77 ms. The bar chart above shows every period we have measured.
The registry lists VibeRaven as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect VibeRaven?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does VibeRaven need an API key?
No. VibeRaven completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
Is VibeRaven open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 61 stars on GitHub and 19 open issues. The licence covers the code in the repository, not the hosted service at viberaven.dev, which runs on its operator's own terms.