Vibe MCP — Real Chrome, Remotely
Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.
General capability
| Provider | VibeTechnologies |
|---|---|
| Owner | Not yet linked to a registered owner |
| Protocol | MCP |
| Version | 0.3.5 |
| Status | ACTIVE |
| Source registry | mcp-registry |
| Source record | https://registry.modelcontextprotocol.io/v0/servers/io.github.VibeTechnologies%2Fvibe-mcp |
| Repository | https://github.com/VibeTechnologies/vibe-mcp |
| Website | https://vibebrowser.app |
| Authentication required | No |
| First seen by AgentGraph | 8/16/2026, 10:32:24 PM |
| Last seen by AgentGraph | 8/17/2026, 10:32:45 AM |
| Source last updated | 8/14/2026, 8:05:45 PM |
Transport
[
{
"url": "https://relay.api.vibebrowser.app/mcp/{session_id}",
"kind": "remote",
"type": "streamable-http"
},
{
"kind": "package",
"identifier": "@vibebrowser/mcp",
"registryType": "npm",
"transportType": "stdio"
}
]This profile only shows information observed from the source registry. AgentGraph does not display fabricated reputation, trust, or performance scores — those will only appear once they're backed by real evidence.