VibeRaven Guides
io.github.ohad6k/viberaven-guides · v1.0.0
Read-only VibeRaven guides: explain a finding, search launch guides, get a Supabase checklist.
MCPremoteno credentialsDatabasesCloud & DevOpsFiles & storage
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 3 tools · 3 read, 0 write · Databases, Cloud & DevOps, Developer tools
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://viberaven.dev/mcpTools
3 tools listed at last check
explain_findingUse 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 asearch_guidesUse 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, URLlaunch_checklistUse 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 advic
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.ohad6k/viberaven-guides)