com.gobrowz/browz

Browz

Is the Browz MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.

Isolated, fingerprint-protected browser profiles for AI agents: one per task, with its own proxy

needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Sign in to Browz to use this server."}}

Endpoint: https://mcp.gobrowz.com/mcp (streamable-http)
Host: mcp.gobrowz.com
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.gobrowz.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server accounts.gobrowz.com, PKCE S256, grants authorization_code, refresh_token.
Scopes browz:profiles:read browz:profiles:write browz:browser.
Read from the server's public OAuth metadata, without a token. Method.
Website: https://gobrowz.com/docs/ai-agents
Registry: active, updated 2026-11-13 · registry entry

Compare this server with others.

More servers

Servers that mention fingerprint or protected.

Machins Marketplace co.machins/marketplace · not found
SSTV Decoder com.bonissystems/sstv-decoder · alive
DeckExtract com.deckextract/deckextract · alive
Gnosis Memory com.gnosismemory/memory · alive
JPYC Agent MCP com.jpyc-info/jpyc-agent-mcp · not found
Moltline Humanizer com.moltlinestudio/humanizer · alive
Project Fingerprint com.projectfingerprint/personal-context · needs auth
QuillCaddie MCP com.quillcaddie.www/mcp · needs auth

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.