io.github.ohad6k/viberaven-guides · v1.0.0 · data-and-databases
VibeRaven Guides is healthy: it completed an MCP handshake in 3298 ms and exposes 3 tools.
Read-only VibeRaven guides: explain a finding, search launch guides, get a Supabase checklist.
Endpoint: https://viberaven.dev/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 3298 ms |
| Last checked (UTC) | 2026-10-15T06:15:48.809Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T06:15:48.809Z | Healthy | 3298 |
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.11 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 |
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 |
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 viberaven@1.6.11 check`), which is advic |