Security & Testing

viberaven.dev

Provides tools to explain VibeRaven security findings and answer launch questions for AI-built apps on Vercel and Supabase.

1 endpoint3 known toolsFirst detected July 6, 2026Last detected October 6, 2026

ENDPOINT 1

https://viberaven.dev/mcp

No auth detected

MCP server metadata

Name: viberaven
Version: 1.5.3

Capabilities

tools

Server instructions

VibeRaven is a repository check for AI-built apps that deploy on Vercel and use Supabase. It is advice, not a gate, and it is not a live database or security test. This server cannot see the user's repository, database, dashboards or Vercel project: it returns the explanations, guides and checklists published on viberaven.dev. The checks themselves run locally in the user's project with `npx -y viberaven@1.5.3 check`. Do not present a result from this server as a scan of the user's app.

Known tools 3

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.

Inferred read-only

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.

Inferred read-only

launch_checklist

Use this when the user wants a manual pre-launch checklist for a Lovable + Supabase app or a Next.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.viberaven]
url = "https://viberaven.dev/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: viberaven
Remote MCP URL: https://viberaven.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "viberaven",
  "transport": "streamable-http",
  "url": "https://viberaven.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.