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.

Vibe MCP — Real Chrome, Remotely

NPM · @VIBEBROWSER/MCP · 2 COMPONENTS · SCANNED AUG 17

Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.

Available components

remote · relay.api.vibebrowser.app 28 npm · @vibebrowser/mcp 71
+7 this week 71 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security88
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects chrome-devtools-mcp 0.21.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 128 tokens (~128/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @vibebrowser/mcp

# add to Claude Code
claude mcp add vibetechnologies-vibe-mcp -- npx -y @vibebrowser/mcp
# add to Codex CLI
codex mcp add vibetechnologies-vibe-mcp -- npx -y @vibebrowser/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vibetechnologies-vibe-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@vibebrowser/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vibetechnologies-vibe-mcp --command npx --arg -y --arg @vibebrowser/mcp
# ~/.hermes/config.yaml
mcp_servers:
  vibetechnologies-vibe-mcp:
    command: "npx"
    args: ["-y", "@vibebrowser/mcp"]
// mcp.json
{
  "mcpServers": {
    "vibetechnologies-vibe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vibebrowser/mcp"
      ]
    }
  }
}
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.

  • 16 Aug 26 +1

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

  • 15 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Aug 26 −11
    • Malware scan: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Schema quality: 99 → 128 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.23 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.2 → 0.3.5 functional
    • Package version: 0.3.2 → 0.3.4 functional
  • 11 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 64

    First indexed and scored.

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 17 Aug 2026 · Analysed npm/@vibebrowser/mcp@0.3.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-3pvj-jv98-qhjq CVE-2026-53765 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L yes
Dependencies 98 packages
Packages resolved 98
Stale 30
Tree resolution Complete
MCP tools · 1 exposed · ~128 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.

Tool Tokens
set_remote ~128

Set the remote relay target for this MCP server. If browser tools are missing, call set_remote first to connect to a Vibe relay using the MCP connector URL from extension Settings, a bare extension UUID, or a ws(s) relay URL. The UUID is the sole bearer credential for the relay session.

NameTypeReqDescription
urlstringyesRemote target: the MCP connector URL from the Vibe extension (https://relay.api.vibebrowser.app/mcp/<extension-uuid>), a bare extension UUID, or a ws(s) relay URL. Call set_remote first when browser…

No output schema declared.

No examples provided.