Skip to content
VibeRaven logo

VibeRaven MCP server

Which MCP servers are VibeRaven's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-22

← Back to VibeRaven

Whose server it is
  • Addresshttps://viberaven.dev/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on viberaven.dev when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools4
  • Server calls itselfviberaven
  • Server version1.6.12
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 287 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer153 ms
  • Space in an agent's context≈ 1,180 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-28
  • 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…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "viberaven": {
      "type": "http",
      "url": "https://viberaven.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http viberaven https://viberaven.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://viberaven.dev/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.