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 OCT 2

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 0 npm · @vibebrowser/mcp 81
0 this week 81 Trust /100
Trust breakdown (7 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 → Why this is hard to 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
  • 31 of 95 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 Management93
  • Stability observed for 28 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Vibe MCP — Real Chrome, Remotely server?

Vibe MCP — Real Chrome, Remotely runs locally as an npm package, launched with npx -y @vibebrowser/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @vibebrowser/mcp

# add to Claude Code
claude mcp add vibetechnologies-vibe-mcp -- npx -y @vibebrowser/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "vibetechnologies-vibe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vibebrowser/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vibetechnologies-vibe-mcp": {
      "command": "npx",
      "args": [
        "-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"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vibetechnologies-vibe-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@vibebrowser/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add vibetechnologies-vibe-mcp -t stdio -c npx -a -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.

  • 2 Oct 26 +1

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

  • 30 Sept 26 +1

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

  • 28 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1
    • Stability: 0.97 → pass security
  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
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 2 Oct 2026 · Analysed npm/@vibebrowser/mcp@0.3.6

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

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

Background: What a vulnerability scan can and cannot prove →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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

Common questions

What is the Vibe MCP — Real Chrome, Remotely server?

Vibe MCP — Real Chrome, Remotely is listed in the public MCP registry as io.github.VibeTechnologies/vibe-mcp. Drive your real, logged-in Chrome from any MCP client, even from a remote machine, no inbound port. This page covers its npm package (@vibebrowser/mcp).

Is the Vibe MCP — Real Chrome, Remotely server safe to use?

Vibe MCP — Real Chrome, Remotely scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 2 October 2026. It declares no install or post-install scripts. 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 Vibe MCP — Real Chrome, Remotely server expose?

Vibe MCP — Real Chrome, Remotely exposes 1 tool: set_remote. Their descriptions and schemas cost roughly 128 tokens of context every time the server is loaded.

Is the Vibe MCP — Real Chrome, Remotely server still maintained?

Vibe MCP — Real Chrome, Remotely is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Vibe MCP — Real Chrome, Remotely server under?

Vibe MCP — Real Chrome, Remotely declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.