Browserbase MCP Server ↗
Browserbase MCP Server is an officially published MCP server from Browserbase. Anomity scores its risk at 10 out of 100 (low).
Analysis summary
Browserbase MCP Server is an officially published MCP server from Browserbase. Anomity scores its risk at 10 out of 100 (low).
Browserbase runs headless browsers in the cloud and exposes them to agents over MCP, so browser automation happens on their infrastructure rather than on the developer's machine — useful for scale, sessions, and not handing a local browser to a model.
It declares browser control and outbound network access. Moving the browser off your machine changes the risk shape rather than removing it: the automation no longer touches your local profile, but the pages, credentials, and session state now live with a third party. For authenticated automation, that means your logged-in sessions exist in someone else's infrastructure — a reasonable trade for many workloads, but one to make deliberately.
Why this entry scored 10 out of 100
This profile starts at the catalog's neutral base of 50. Because the entry is officially published, trust adjusts the score by -40. The entry declares no high-risk capabilities on its own, so capabilities add nothing. It matches no dangerous capability combinations. The clamped result is 10, placing it in the low band.
Findings
-
Published by the vendor Trust offset
Capabilities
Every capability the entry declares, with the security implication of each.
-
browser:controlBrowser controlDrives a browser session. Combined with credential access can impersonate the user on web services. -
network:outboundOutbound networkCan make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access.