Skip to content

VibeRaven MCP server

io.github.ohad6k/viberaven-guidesohad6kstreamable-httpv1.1.0Scanned

Check Supabase migrations for RLS and grant gaps; fixes for Supabase, Vercel, Stripe errors.

7 tools: 5 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 5 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the VibeRaven MCP server can do

The VibeRaven MCP server is published by the GitHub account ohad6k. It has 7 tools. It can create or change data (5 tools: check_supabase_migrations, check_github_repo, provider_playbook, recent_provider_changes and 1 more), but cannot delete data. 2 tools only read.

1 tool reads private data (search_guides); 1 tool brings in text other people can write (check_github_repo).

The fixed checks matched 2 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 5Claude Code: ask
  • check_github_repocheck_github_repo({"repo":"owner/name"}) Check the Supabase migrations of a public GitHub repository for missing RLS or policies, policies that let anyone read or write every row, …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    check_github_repo({"repo":"owner/name"}) Check the Supabase migrations of a public GitHub repository for missing RLS or policies, policies that let anyone read or write every row, exposed security definer functions and Data API grant gaps. Use it when the user names or links their app repo (Lovable, Bolt, v0 and Cursor apps synced to GitHub) and has no terminal. Reads supabase/migrations/*.sql at one commit with the VibeRaven 1.7.11 SQL rules and returns finding id, severity, file, line, a link to that line, a fix and a guide link. Limits: public repositories only, up to 50 files/200 KB; cannot see the live database or private repos, does not run SQL, and does not store files.

    Annotations the server declares

    • title: Check a public GitHub repo for Supabase RLS gaps
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true
  • check_supabase_migrationscheck_supabase_migrations({"sql":"create table public.notes (id bigint);"}) Use when reviewing Supabase migration changes for missing RLS or policies, unrestricted read/write polic…1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.sql), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "check_supabase_migrations" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.sql), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    check_supabase_migrations({"sql":"create table public.notes (id bigint);"}) Use when reviewing Supabase migration changes for missing RLS or policies, unrestricted read/write policies, exposed security definer functions and Data API grant gaps. Pass file contents: sql contains one migration's SQL text; files contains path and content for each file. Runs the VibeRaven 1.7.11 SQL rules and returns finding id, severity, file, line, a suggested fix and a guide link. For missing Data API grants, include the migration revoking default privileges or supabase/config.toml, plus browser files using supabase.from(...) (a "use client" file, or src files with package.json for Vite). Limits: supplied text only, up to 200 KB/50 files; cannot access your repository or database, does not execute SQL, and does not store or log file contents.

    Annotations the server declares

    • title: Check Supabase migrations for RLS and grant gaps
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • launch_checklistlaunch_checklist({"stack":"nextjs-supabase-vercel"}) Use for a broad pre-launch review of a Lovable + Supabase app or a Next.js + Supabase app on Vercel.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    launch_checklist({"stack":"nextjs-supabase-vercel"}) Use for a broad pre-launch review of a Lovable + Supabase app or a Next.js + Supabase app on Vercel. For a specific failing request, use search_guides. Returns a published manual checklist with sources and an optional local repo check (`npx -y viberaven@1.7.11 check`). Limits: checklist guidance only; does not run checks or verify dashboards, code or launch readiness.

    Annotations the server declares

    • title: Get a launch checklist
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • provider_playbookprovider_playbook({"provider":"supabase","topic":"grants"}) Use before implementing a feature that touches a provider, when setup or integration rules are needed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    provider_playbook({"provider":"supabase","topic":"grants"}) Use before implementing a feature that touches a provider, when setup or integration rules are needed. Returns versioned setup guidance, gotchas, dated changes, integration seams, existing repo checks and planned live checks with official sources. Available packs: supabase. Pass topic to return matching items; for a specific error use search_guides, for dated changes use recent_provider_changes. Limits: guidance only; does not connect to providers, read your project, run checks or verify that a feature works.

    Annotations the server declares

    • title: Get a provider playbook
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • recent_provider_changesrecent_provider_changes({"provider":"supabase","query":"42501","limit":5}) Use when a provider update may explain changed behavior, or a deployment needs review against dated provi…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.query.description mentions "credentials".

      Matched text

      inputSchema.properties.query.description: "...d error text or public keywords. Remove credentials, private paths and personal data before..."

      What this check looks for
    Description, as the server wrote it
    recent_provider_changes({"provider":"supabase","query":"42501","limit":5}) Use when a provider update may explain changed behavior, or a deployment needs review against dated provider changes. Returns candidate changes, documented errors or symptoms, fixes, date meanings and official supporting sources. Filter by provider or redacted error keywords. For general troubleshooting use search_guides; for setup use provider_playbook. Available providers: anthropic, clerk, lovable, nextjs, openai, railway, stripe, supabase, vercel. Limits: guidance only; does not read your repo, connect to providers, run fixes or verify rollout, deployment or live behavior.

    Annotations the server declares

    • title: Check recent provider changes
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 2Show 2 read-only tools
  • explain_findingexplain_finding({"gap_id":"rls_disabled"}) Use after a check returns a finding id, such as rls_disabled or env_var_drift, to understand and fix that VibeRaven 1.7.11 finding.No findings

    Why it is in this group

    • The name "explain_finding" says "explain": a word for reading.
    Description, as the server wrote it
    explain_finding({"gap_id":"rls_disabled"}) Use after a check returns a finding id, such as rls_disabled or env_var_drift, to understand and fix that VibeRaven 1.7.11 finding. Returns detection scope, impact, fix guidance and coverage limits quoted from viberaven.dev with source links. Unknown ids return found: false and known ids. For a raw error without a finding id, use search_guides. Limits: explains published rules only; does not read your repo, database or Vercel project.

    Annotations the server declares

    • title: Explain a VibeRaven finding
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • search_guidessearch_guides({"query":"supabase tables missing rls"}) Find troubleshooting steps for exact errors in Supabase RLS, Realtime and auth; Clerk middleware and sessions; Better Auth or…Reads private dataNo findings

    Why it is in this group

    • The name "search_guides" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "table": it reads databases.
    Description, as the server wrote it
    search_guides({"query":"supabase tables missing rls"}) Find troubleshooting steps for exact errors in Supabase RLS, Realtime and auth; Clerk middleware and sessions; Better Auth origins and OAuth callbacks; Vercel environment variables and deployments; Stripe webhooks; or Storybook environment variables and 404s. Search published viberaven.dev guides by keywords or error text; returns up to 5 titles, URLs and short answers. Also covers Lovable + Supabase launch checks and client handoff. No match returns an empty list. Limits: searches the indexed published guides only; does not browse the web or read your project.

    Annotations the server declares

    • title: Search VibeRaven launch guides
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://viberaven.dev/mcp: tools/list returned 8 tools to an anonymous client, including race_two_users (write), check_supabase_migrations (write), check_github_repo (write), provider_playbook (write), recent_provider_changes (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 5 to 6
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 3 to 5
  3. Oct 29, 2026
    • Tools that change things, listed without credentials: 1 to 3

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "check_supabase_migrations" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.sql), which can change anything it can reach.

    What this check looks for
  • The input schema at properties.query.description mentions "credentials".

    Matched text

    inputSchema.properties.query.description: "...d error text or public keywords. Remove credentials, private paths and personal data before..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
    • Tools that change things, listed without credentials: 5 to 6
  2. Tools3 added, 4 changed.+3 added~4 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 5.View diff
    • Tools that change things, listed without credentials: 3 to 5
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 3.View diff
    • Tools that change things, listed without credentials: 1 to 3
  5. Tools1 added.+1 addedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__viberaven-guides__explain_finding",
      "mcp__viberaven-guides__search_guides"
    ],
    "ask": [
      "mcp__viberaven-guides__check_supabase_migrations",
      "mcp__viberaven-guides__check_github_repo",
      "mcp__viberaven-guides__provider_playbook",
      "mcp__viberaven-guides__recent_provider_changes",
      "mcp__viberaven-guides__launch_checklist"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as viberaven-guides. Review it before you use it.

Capability tags behind 2 rules
  • mcp__viberaven-guides__check_github_repo untrusted-input
  • mcp__viberaven-guides__search_guides private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ohad6k/viberaven-guides/verify?hash=7d859004a838c14d34c47b04f775800054586c6705e021f5935e7e45b33ae69a" | jq -e '.changed == false'

Pinned hash 7d859004a838, from Nov 9, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ohad6k/viberaven-guides/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ohad6k/viberaven-guides
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ohad6k/viberaven-guides.svg)](https://radar.anlyon.com/servers/io.github.ohad6k/viberaven-guides)

Source: MCP Registry · repository. Synced Oct 27, 2026, 18:18 UTC.

VibeRaven MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the VibeRaven MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the VibeRaven MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the VibeRaven MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the VibeRaven MCP server have?

7 tools: 5 write, 2 read. check_supabase_migrations, check_github_repo, provider_playbook, recent_provider_changes, launch_checklist, explain_finding and search_guides.

Does the VibeRaven MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the VibeRaven MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the VibeRaven MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.