# VibeRaven Guides (remote · viberaven.dev)

Read-only VibeRaven guides: explain a finding, search launch guides, get a Supabase checklist.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `viberaven.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ohad6k-viberaven-guides/viberaven.md), [page](https://verifymcp.io/servers/ohad6k-viberaven-guides/viberaven)

## Channel facts

- Endpoint: `https://viberaven.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http ohad6k-viberaven-guides 'https://viberaven.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ohad6k-viberaven-guides": {
      "url": "https://viberaven.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ohad6k-viberaven-guides": {
      "type": "http",
      "url": "https://viberaven.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ohad6k-viberaven-guides]
url = "https://viberaven.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ohad6k-viberaven-guides": {
      "type": "remote",
      "url": "https://viberaven.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ohad6k-viberaven-guides --url 'https://viberaven.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ohad6k-viberaven-guides:
    url: "https://viberaven.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ohad6k-viberaven-guides": {
      "Transport": "http",
      "Url": "https://viberaven.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ohad6k-viberaven-guides -t streamable-http -u 'https://viberaven.dev/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-07 (score 76, +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.

### 2026-10-04 (score 75, +1)

- [security] 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
- [functional] Server version: 1.6.1 → 1.6.2

### 2026-10-02 (score 74, 0)

- [security] 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
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.5.3 → 1.6.1

### 2026-10-01 (score 74)

First indexed and scored.

## MCP tools (3)

### `explain_finding` (~200 tokens)

Explain a VibeRaven 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.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.

Input parameters:

- `gap_id` (string, required): The finding id as printed by VibeRaven, for example rls_disabled.

Output parameters:

- `detects` (array)
- `does_not_check` (array)
- `found` (boolean)
- `gap_id` (string)
- `how_to_fix` (array)
- `known_ids` (array)
- `named_on` (string)
- `viberaven_version` (string)
- `why_it_matters` (array)

### `search_guides` (~139 tokens)

Search VibeRaven launch 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. 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.

Input parameters:

- `query` (string, required): A few keywords from the question, for example "supabase tables missing rls".

Output parameters:

- `results` (array)

### `launch_checklist` (~155 tokens)

Get a launch checklist

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.

Input parameters:

- `stack` (string, required): lovable-supabase for a Lovable app with Supabase, nextjs-supabase-vercel for a Next.js app with Supabase deployed on Vercel.

Output parameters:

- `items` (array)
- `optional_repo_check` (object)
- `short_answer` (string)
- `sources` (array)
- `stack` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ohad6k-viberaven-guides/viberaven#diagnostics

## Score history

- 2026-10-07: 76
- 2026-10-05: 75
- 2026-10-04: 75
- 2026-10-03: 74
- 2026-10-02: 74
- 2026-10-01: 74

## Common questions

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

## Links

- Remote endpoint: https://viberaven.dev/mcp
- Website: https://viberaven.dev/
- Changelog RSS feed: https://verifymcp.io/servers/ohad6k-viberaven-guides/viberaven.xml
- Changelog JSON feed: https://verifymcp.io/servers/ohad6k-viberaven-guides/viberaven.json
- HTML version of this page: https://verifymcp.io/servers/ohad6k-viberaven-guides/viberaven