← viberaven.dev

INDIVIDUAL MCP TOOL

check_supabase_migrations

Review Supabase migration changes for missing RLS or policies, unrestricted read/write policies, exposed security definer functions and Data API grant gaps.

viberaven.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://viberaven.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for check_supabase_migrations and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.

Parent server

viberaven.dev

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.

Related tools

  • provider_playbook — Plan setup and integration before implementing a feature that touches a provider.
  • recent_provider_changes — Check dated official provider guidance before answering a provider error or updating a deployment.
  • explain_finding — Understand and fix a finding from a VibeRaven 1.
  • search_guides — Find troubleshooting steps for Supabase RLS, Realtime and auth callbacks, Vercel environment variables and deployment errors, or Stripe webhooks after deploy.
  • launch_checklist — Prepare a Lovable + Supabase app or a Next.