# VibeScale (remote · vibe.elya-studio.com)

For app builders in Israel: pre-launch checks for leaked keys, Supabase RLS, exposed env vars.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `vibe.elya-studio.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/ranqint-vibescale/vibe.md), [page](https://verifymcp.io/servers/ranqint-vibescale/vibe)

## Channel facts

- Endpoint: `https://vibe.elya-studio.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **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. 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.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 598 tokens (~199/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**: 30/100
  - Stability observed for 9 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.
- **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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the VibeScale MCP server?

VibeScale is a hosted endpoint at https://vibe.elya-studio.com/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 ranqint-vibescale 'https://vibe.elya-studio.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ranqint-vibescale": {
      "url": "https://vibe.elya-studio.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ranqint-vibescale": {
      "type": "http",
      "url": "https://vibe.elya-studio.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ranqint-vibescale]
url = "https://vibe.elya-studio.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ranqint-vibescale": {
      "type": "remote",
      "url": "https://vibe.elya-studio.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ranqint-vibescale --url 'https://vibe.elya-studio.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ranqint-vibescale:
    url: "https://vibe.elya-studio.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ranqint-vibescale": {
      "Transport": "http",
      "Url": "https://vibe.elya-studio.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ranqint-vibescale -t streamable-http -u 'https://vibe.elya-studio.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ranqint-vibescale": {
      "type": "http",
      "url": "https://vibe.elya-studio.com/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-11-20 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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-11-16 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 73)

First indexed and scored.

## MCP tools (3)

### `scan_app_launch_readiness` (~187 tokens)

Scan a live web app for leaked keys and missing protections

Reads one public web app the way a browser does (its HTML, the same-site scripts it loads and any source maps they point to) and reports what any visitor can already see: server secret keys shipped to the browser (Supabase service_role, OpenAI, Anthropic, Stripe, AWS, GitHub, SendGrid, Resend; shown masked), a published source map, no HTTPS, and missing Content-Security-Policy, HSTS or frame protection. Use when someone built an app with Lovable, Base44, Bolt, Cursor, Replit or similar and asks whether it is safe to launch or whether a key leaked. It does not sign in, guess paths or query the app's database. Findings are in Hebrew.

Input parameters:

- `url` (string, required): The public address of the app, e.g. my-app.lovable.app or https://example.com

### `lint_supabase_rls` (~154 tokens)

Check Supabase SQL for row level security gaps

Reads Supabase SQL (migrations or a schema dump) as text and lists tables in exposed schemas without row level security, RLS with no policy, policies that allow everything or read user_metadata, policies without a role, write grants to anon, SECURITY DEFINER functions and views, new tables without a grant, and public storage buckets, each with SQL that fixes it. Use when someone asks whether their Supabase database is locked down, or before launching an app that uses Supabase. The SQL is never executed or stored; policy logic (who should see what) is not judged. Findings are in Hebrew.

Input parameters:

- `sql` (string, required): The SQL text: one or more migration files or a schema dump

### `check_env_exposure` (~157 tokens)

Check which environment variables reach the browser

Takes environment variable NAMES (never values) and says, for each one, whether the build tool ships it to every visitor (VITE_, NEXT_PUBLIC_, EXPO_PUBLIC_, REACT_APP_, PUBLIC_, GATSBY_, NUXT_PUBLIC_) and whether its name looks like a server secret that must not be there. Use when someone asks whether their .env or API keys are exposed in a Lovable, Bolt, Vite, Next.js or Expo app. Send names only; if a value is included it is dropped and not stored. Explanations are in Hebrew.

Input parameters:

- `names` (array, required): Variable names, e.g. ["VITE_SUPABASE_URL", "VITE_OPENAI_API_KEY"]

## Diagnostics

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

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73

## Common questions

### What is the VibeScale MCP server?

VibeScale is an MCP server listed in the public MCP registry as io.github.Ranqint/vibescale. For app builders in Israel: pre-launch checks for leaked keys, Supabase RLS, exposed env vars. This page covers its hosted endpoint (https://vibe.elya-studio.com/mcp).

### Is the VibeScale MCP server safe to use?

VibeScale scores 77 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 VibeScale MCP server expose?

VibeScale exposes 3 tools: scan_app_launch_readiness, lint_supabase_rls, check_env_exposure. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.

### Does the VibeScale MCP server require authentication?

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

### Is the VibeScale MCP server still maintained?

VibeScale is still listed as active in the MCP registry. We last reached this channel on 21 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 VibeScale MCP server?

VerifyMCP ran 13 checks on VibeScale, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.

## Links

- Remote endpoint: https://vibe.elya-studio.com/mcp
- Website: https://vibe.elya-studio.com/tools/chatgpt-claude
- Changelog RSS feed: https://verifymcp.io/servers/ranqint-vibescale/vibe.xml
- Changelog JSON feed: https://verifymcp.io/servers/ranqint-vibescale/vibe/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ranqint-vibescale/vibe.json
- HTML version of this page: https://verifymcp.io/servers/ranqint-vibescale/vibe
