Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VibeRaven

REMOTE · VIBERAVEN.DEV

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

Available components

0 this week 88 Trust /100

Last scanned (16 minutes ago)

Scores higher than 95% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1452 tokens (~161/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_github_repo” rewrote its description, which is the text the model reads security
    • Tool “provider_playbook” rewrote its description, which is the text the model reads security
    • Tool “search_guides” rewrote its description, which is the text the model reads security
  • 21 Nov 26 0
    • Resource “check-report” now points somewhere else: ui://viberaven/check-report-v6.html → ui://viberaven/check-report-v7.html security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_supabase_migrations” rewrote its description, which is the text the model reads security
    • Tool “race_two_users” rewrote its description, which is the text the model reads security
    • Schema quality: 212 → 164 ▲ functional
    • Schema quality: excellent → good functional
    • Tool “check_supabase_migrations” changed its title: Check Supabase migrations for RLS and grant gaps → Check Supabase migrations cosmetic
  • 20 Nov 26 0
    • Resource “check-report” now points somewhere else: ui://viberaven/check-report-v5.html → ui://viberaven/check-report-v6.html security
  • 19 Nov 26 0
    • Tool “race_two_users” rewrote its description, which is the text the model reads security
  • 18 Nov 26 0
    • Resource “check-report” now points somewhere else: ui://viberaven/check-report-v4.html → ui://viberaven/check-report-v5.html security
  • 17 Nov 26 0
    • Resource “check-report” now points somewhere else: ui://viberaven/check-report-v3.html → ui://viberaven/check-report-v4.html security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_github_repo” rewrote its description, which is the text the model reads security
    • Tool “check_supabase_migrations” rewrote its description, which is the text the model reads security
    • Tool “explain_finding” rewrote its description, which is the text the model reads security
    • Tool “launch_checklist” rewrote its description, which is the text the model reads security
    • Schema quality: 182 → 207 ▼ functional
    • Tool coverage: 100% → 82% ▼ functional
    • Server version: 1.8.0 → 1.10.0 functional
    • New tool “race_two_users” functional
  • 10 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_github_repo” rewrote its description, which is the text the model reads security
    • Tool “check_supabase_migrations” rewrote its description, which is the text the model reads security
    • Tool “explain_finding” rewrote its description, which is the text the model reads security
    • Tool “launch_checklist” rewrote its description, which is the text the model reads security
    • Server version: 1.7.11 → 1.8.0 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_github_repo” rewrote its description, which is the text the model reads security
    • Tool “check_supabase_migrations” rewrote its description, which is the text the model reads security
    • Tool “explain_finding” rewrote its description, which is the text the model reads security
    • Tool “launch_checklist” rewrote its description, which is the text the model reads security
    • Server version: 1.7.8 → 1.7.11 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Probed https://viberaven.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=viberaven.dev CN=YR1,O=Let's Encrypt,C=US 28 Sept 2026 27 Dec 2026 RSA 2048 SHA256-RSA 68629c5fd1419f07e936ee79dde7a7022f3
SANs: viberaven.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of viberaven.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
viberaven.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://viberaven.dev/mcp Verified 200
http (plaintext) http://viberaven.dev/mcp HTTPS enforced 308 https://viberaven.dev/mcp
MCP tools · 8 exposed · ~1,332 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_github_repo ~229

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. Call when the user asks for a migration, RLS or grants review of a named public GitHub repository, even with a terminal. Pass the URL in repo and the requested revision in ref. Reads supabase/migrations/*.sql at one commit with the VibeRaven 1.10.0 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.

NameTypeReqDescription
refstring–Optional branch, tag or commit. Default: the default branch.
repostringyesThe public GitHub repository: https://github.com/owner/name, github.com/owner/name or owner/name.
NameTypeReqDescription
access_summaryarray––
corrected_sqlstring––
countsobjectyes–
findingsarrayyes–
findings_not_listedintegeryes–
full_checkobjectyes–
nextStepobject––
public_tablesintegeryes–
race_next_stepstring––
repositoryobjectyes–
scopestringyes–
skippedarrayyes–
sql_filesarrayyes–
viberaven_versionstringyes–

No examples provided.

check_supabase_migrations ~101

Statically checks supplied Supabase migration text for RLS, Data API grants and supported concurrent-write patterns. Pass pasted SQL in sql or file contents in files. For supported repairs, returns corrected_sql and a race_spec for race_two_users.

NameTypeReqDescription
filesarray–Several files: .sql migrations, and optionally supabase/config.toml, package.json and browser code files.
sqlstring–The SQL text of one migration file.
NameTypeReqDescription
access_summaryarray––
corrected_sqlstring––
countsobjectyes–
findingsarrayyes–
findings_not_listedintegeryes–
full_checkobjectyes–
nextStepobject––
public_tablesintegeryes–
race_next_stepstring––
scopestringyes–
skippedarrayyes–
sql_filesarrayyes–
viberaven_versionstringyes–

No examples provided.

explain_finding ~146

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.10.0 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.

NameTypeReqDescription
gap_idstringyesThe finding id as printed by VibeRaven, for example rls_disabled.
NameTypeReqDescription
detectsarray––
does_not_checkarray––
foundbooleanyes–
gap_idstring––
how_to_fixarray––
known_idsarray––
named_onstring––
nextStepobject––
viberaven_versionstringyes–
why_it_mattersarray––

No examples provided.

launch_checklist ~151

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.10.0 check`). Limits: checklist guidance only; does not run checks or verify dashboards, code or launch readiness.

NameTypeReqDescription
stackstringyeslovable-supabase for a Lovable app with Supabase, nextjs-supabase-vercel for a Next.js app with Supabase deployed on Vercel.
NameTypeReqDescription
itemsarrayyes–
nextStepobject––
optional_repo_checkobjectyes–
short_answerstringyes–
sourcesarrayyes–
stackstringyes–
titlestringyes–
urlstringyes–

No examples provided.

provider_playbook ~198

provider_playbook({"provider":"supabase","topic":"grants"}) Call for a Supabase RLS, policy or Data API grants question when you need the documented setup or role behavior. Use a short topic such as rls or grants. 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.

NameTypeReqDescription
providerstringyesProvider id, for example supabase. Unsupported ids return the available packs.
topicstring–Optional words for the part you need, for example "grants" or "auth redirect". Only matching items are returned; with no match, the whole pack.
NameTypeReqDescription
nextStepobjectyes–
packobjectyes–
packHashstringyes–
packVersionstringyes–
providerstringyes–
topicobject––
verificationobjectyes–

No examples provided.

race_two_users ~115

Runs bounded checks in offline PostgreSQL. For a migration repair, pass corrected_sql as sql and its race_spec as spec. A completed passing repair check saves a shareable summary-only Proof Record. Portable v1 and legacy actor specs are also accepted.

NameTypeReqDescription
githubobject––
maxOrdersinteger––
replayTokenstring–From a previous result. Send the same input including maxOrders.
spec–yes–
sqlstring–Complete migration SQL, not a database connection string.
NameTypeReqDescription
brokenOrdersarray––
capReasonstring|null––
cappedboolean––
codestring––
completeboolean––
coverageobject––
finalRowsobject|null––
fixHintstring––
formatinteger––
kindstringyes–
messagestring––
ordersTotalinteger––
ordersTriedinteger––
proofobject––
proofUnavailableboolean––
replayTokenstring––
retryAfterinteger––
rulestring––
scopestring––
shortestBrokenOrderobject|null––
statusstring––

No examples provided.

recent_provider_changes ~205

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.

NameTypeReqDescription
limitinteger–Maximum entries, 1 to 8; default 5.
providerstring–Optional lowercase provider id. Unsupported ids return the bounded available list.
querystring–Optional redacted error text or public keywords. Remove credentials, private paths and personal data before calling.
NameTypeReqDescription
availableProvidersarrayyes–
correctionsAndConflictsarrayyes–
dateConventionstringyes–
entriesarrayyes–
limitsarrayyes–
nextStepobject––
packHashstringyes–
packVersionstringyes–
reviewedAtstringyes–
verificationobjectyes–

No examples provided.

search_guides ~187

search_guides({"query":"supabase tables missing rls"}) Call with the exact error or a short symptom before offering a troubleshooting fix. Covers 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. Distinguishes a closest guide from a direct match. Limits: searches the indexed published guides only; does not browse the web or read your project.

NameTypeReqDescription
querystringyesA few keywords or the exact error text, for example "supabase tables missing rls". Long text is searched by its first 200 characters.
NameTypeReqDescription
matchstringyes–
nextStepobject––
resultsarrayyes–

No examples provided.

Install

How do I install the VibeRaven MCP server?

VibeRaven is a hosted endpoint at https://viberaven.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · viberaven.dev

# add to Claude Code
claude mcp add --transport http ohad6k-viberaven-guides 'https://viberaven.dev/mcp'
Common questions

What is the VibeRaven MCP server?

VibeRaven is an MCP server listed in the public MCP registry as io.github.ohad6k/viberaven-guides. Check Supabase migrations for RLS and grant gaps; fixes for Supabase, Vercel, Stripe errors. This page covers its hosted endpoint (https://viberaven.dev/mcp).

Is the VibeRaven MCP server safe to use?

VibeRaven scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VibeRaven MCP server expose?

VibeRaven exposes 8 tools: check_supabase_migrations, check_github_repo, provider_playbook, recent_provider_changes, race_two_users, and 3 more. Their descriptions and schemas cost roughly 1,332 tokens of context every time the server is loaded.

Does the VibeRaven MCP server require authentication?

No. We connected to VibeRaven without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VibeRaven MCP server still maintained?

VibeRaven is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the VibeRaven MCP server?

VerifyMCP ran 14 checks on VibeRaven, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.