humanbrowser-cloud-mcp.yml

Human Browser ships the same MCP server two ways: a hosted Streamable HTTP endpoint at https://agent.humanbrowser.cloud/mcp (the host that also serves the A2A endpoint, the agent card and the OAuth discovery documents) and a stdio server inside the npm package @virixlabs/humanbrowser (`npx -y @virixlabs/humanbrowser mcp`). Both take the one hb_live_ bearer token. The hosted endpoint is auth-gated at the transport: an anonymous initialize and tools/list both return HTTP 401 with WWW-Authenticate: Bearer realm="humanbrowser-mcp" and {"error":"unauthorized","hint":"Authorization: Bearer hb_live_"}; a GET returns 405. So the live tool list could not be introspected. The tool list below is the one the provider ships in the package source (mcp/server.js in the 5.0.3 tarball) and repeats in the agent card's MCP section — three tools with real JSON-Schema inputSchemas — and it is recorded as such, not as a live tools/list. The provider's own /docs/mcp page lists a DIFFERENT six-tool surface (spawn_session, run_task, observe_session, list_sessions, close_session, take_screenshot, with readOnlyHint/destructiveHint annotations); which list the hosted endpoint actually returns cannot be settled without a token, and the discrepancy is recorded rather than resolved. RFC 9728 protected-resource metadata for the MCP resource and RFC 8414 authorization-server metadata are both served on the agent host (see well-known/), advertising OAuth 2.1 with PKCE, client-ID metadata documents and scopes mcp:run / mcp:read — but the docs, the card and the package all authenticate with the static bearer token, and the metadata's token_endpoint, registration_endpoint and service_documentation URLs all 404 on GET.

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.