mcp-pulse

io.github.VibeTechnologies/vibe-mcp

Vibe MCP — Real Chrome, Remotely

io.github.VibeTechnologies/vibe-mcp did not answer the probe on 2026-10-03. Result: needs auth (HTTP 401).

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

needs auth probed 2026-10-03 · HTTP 401

Streamable HTTP error: Error POSTing to endpoint: {"error":"Unauthorized","error_description":"Provide the extension UUID as /mcp/<uuid>, an X-Remote-Session: <
Endpoint
https://relay.api.vibebrowser.app/mcp/{session_id} (streamable-http)
Host
relay.api.vibebrowser.app
Repository
https://github.com/VibeTechnologies/vibe-mcp
Website
https://vibebrowser.app
Registry
active, updated 2026-08-21 · registry entry
Reachable
2 of the last 2 probes

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsTokens
2026-10-03 20:36needs auth
2026-10-03 17:52needs auth

Badge

mcp-pulse: needs auth

[![mcp-pulse](https://mcp-pulse.ulehla.dev/badge/io.github.VibeTechnologies/vibe-mcp.svg)](https://mcp-pulse.ulehla.dev/s/io.github.VibeTechnologies/vibe-mcp)