VibeRaven Guides
REMOTE · VIBERAVEN.DEV · SCANNED OCT 7
Read-only VibeRaven guides: explain a finding, search launch guides, get a Supabase checklist.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 614 tokens (~204/item across 3 items; 3 tools + 0 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the VibeRaven Guides MCP server?
VibeRaven Guides 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
claude mcp add --transport http ohad6k-viberaven-guides 'https://viberaven.dev/mcp'
{
"mcpServers": {
"ohad6k-viberaven-guides": {
"url": "https://viberaven.dev/mcp"
}
}
} {
"servers": {
"ohad6k-viberaven-guides": {
"type": "http",
"url": "https://viberaven.dev/mcp"
}
}
} [mcp_servers.ohad6k-viberaven-guides] url = "https://viberaven.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ohad6k-viberaven-guides": {
"type": "remote",
"url": "https://viberaven.dev/mcp",
"enabled": true
}
}
} openclaw mcp add ohad6k-viberaven-guides --url 'https://viberaven.dev/mcp' --transport streamable-http
mcp_servers:
ohad6k-viberaven-guides:
url: "https://viberaven.dev/mcp" {
"McpServers": {
"ohad6k-viberaven-guides": {
"Transport": "http",
"Url": "https://viberaven.dev/mcp"
}
}
} assistant mcp add ohad6k-viberaven-guides -t streamable-http -u 'https://viberaven.dev/mcp'
{
"mcpServers": {
"ohad6k-viberaven-guides": {
"type": "http",
"url": "https://viberaven.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
- The server rewrote its instructions, which are the text every model session 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.6.1 → 1.6.2 functional
- 2 Oct 26 0
- The server rewrote its instructions, which are the text every model session 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
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.5.3 → 1.6.1 functional
- 1 Oct 26 74
First indexed and scored.
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 7 Oct 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. | present | 60074 | 8 | Verified |
| viberaven.dev. | absent | 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 |
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 →
explain_finding Explain a VibeRaven finding ~200
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.5 report. Returns what the rule detects in repository files, why it matters, how to fix it and what it does not check, quoted from viberaven.dev with a source link for each part. It does not read the user's repository, database or Vercel project. Known ids: rls_disabled, rls_no_policies, rls_policy_allows_all_read, rls_policy_allows_all_write, security_definer_function_executable, pooler_port_mismatch, service_role_key_in_client_code, env_var_drift. An unknown id returns found: false and the list of known ids.
| Name | Type | Req | Description |
|---|---|---|---|
| gap_id | string | yes | The finding id as printed by VibeRaven, for example rls_disabled. |
| Name | Type | Req | Description |
|---|---|---|---|
| detects | array | – | – |
| does_not_check | array | – | – |
| found | boolean | yes | – |
| gap_id | string | – | – |
| how_to_fix | array | – | – |
| known_ids | array | – | – |
| named_on | string | – | – |
| viberaven_version | string | yes | – |
| why_it_matters | array | – | – |
No examples provided.
launch_checklist Get a launch checklist ~155
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 VibeRaven step (`npx -y viberaven@1.6.5 check`), which is advice, not a gate. The items are manual checks the user does in their dashboards and code; this tool does not run any of them.
| Name | Type | Req | Description |
|---|---|---|---|
| stack | string | yes | lovable-supabase for a Lovable app with Supabase, nextjs-supabase-vercel for a Next.js app with Supabase deployed on Vercel. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| optional_repo_check | object | yes | – |
| short_answer | string | yes | – |
| sources | array | yes | – |
| stack | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
search_guides Search VibeRaven launch guides ~139
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 keyword and returns up to 5 matches, each with its title, URL and the short answer from the page. It only searches those published pages: it does not browse the web or read the user's project. No match returns an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A few keywords from the question, for example "supabase tables missing rls". |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
What is the VibeRaven Guides MCP server?
VibeRaven Guides is an MCP server listed in the public MCP registry as io.github.ohad6k/viberaven-guides. Read-only VibeRaven guides: explain a finding, search launch guides, get a Supabase checklist. This page covers its hosted endpoint (https://viberaven.dev/mcp).
Is the VibeRaven Guides MCP server safe to use?
VibeRaven Guides scores 76 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 Guides MCP server expose?
VibeRaven Guides exposes 3 tools: explain_finding, search_guides, launch_checklist. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.
Does the VibeRaven Guides MCP server require authentication?
No. We connected to VibeRaven Guides without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VibeRaven Guides MCP server still maintained?
VibeRaven Guides is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.