Human Browser MCP Server
Model Context Protocol access to the same browser runtime, shipped two ways: a hosted Streamable HTTP endpoint at https://agent.humanbrowser.cloud/mcp that requires the hb_live_ bearer token (anonymous initialize and tools/list answer 401 with WWW-Authenticate: Bearer realm="humanbrowser-mcp"; 60 requests per 60 s per token) and a stdio server inside the npm package (`npx -y @virixlabs/humanbrowser mcp`, HB_TOKEN env). The package source exposes three tools — humanbrowser_run, humanbrowser_stream, humanbrowser_viewer_url — with JSON-Schema inputSchemas; the provider's MCP docs page describes a different six-tool surface that could not be verified. RFC 9728 protected-resource metadata names this endpoint as an OAuth resource (scopes mcp:run, mcp:read) with an authorization server on the same host.