Vibe MCP — Real Chrome, Remotely MCP server
Checked 2026-09-07. Alive: yes. Handshake: unknown.
Category: browser-automation. API and field schema.
Facts
| id | vibetechnologies--vibe-mcp |
| name | Vibe MCP — Real Chrome, Remotely |
| registry_name | io.github.VibeTechnologies/vibe-mcp |
| repo_url | https://github.com/VibeTechnologies/vibe-mcp |
| endpoint_url | https://relay.api.vibebrowser.app/mcp/{session_id} |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | unknown |
| handshake_checked_at | 2026-09-07T19:01:42Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:401 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | jsonrpc |
| handshake_latency_ms | 5156 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-08-23T07:19:43Z |
| category | browser-automation |
| license_spdx | Apache-2.0 |
How to install or connect
Connect your MCP client to https://relay.api.vibebrowser.app/mcp/{session_id}.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.