BrowserStack MCP (remote)

70/100

Capped at 70: no passing tool call yet; the tests add up to 75. Why scores are capped

Last tested 2026-11-06 (Fresh: tested within 30 days) Needs credentialsNo tool call tested yet OAuth

Advisories: not checked (remote-only)

Security review: not tested

Test points add up to 75; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (75/100)

  • Install20/20
  • Handshake5/30
  • Maintenance25/25
  • Docs15/15
  • License10/10

What we probed (2026-11-06 UTC, no credentials): an MCP initialize POST to https://mcp.browserstack.com/mcp returned HTTP 401 with an OAuth challenge (WWW-Authenticate resource_metadata https://mcp.browserstack.com/.well-known/oauth-protected-resource); that metadata lists authorization server https://mcp.browserstack.com and resource https://mcp.browserstack.com/mcp. We did not sign in or use BrowserStack username/access key, so no tools were listed or called. The local npm package @browserstack/mcp-server 2.6.1 installs but exits unless BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY are set. Source: browserstack/mcp-server (AGPL-3.0; 154 GitHub stars when tested). Vendor docs at browserstack.com/docs/browserstack-mcp-server state the remote endpoint and OAuth client setup. Score capped: no tool call.
Claude Code 2.1.321 fixed MCP OAuth requests sending secrets such as refresh tokens to another host when a server redirected them. Claude Code changelog

Transport: Streamable HTTP · not tested

Token cost (estimate): the figure is pending. We have no tools/list capture to estimate from.

Permissions: tool permissions pending · Auth: OAuth · Rate limit: unknown · Pricing unit: unknown

Auth: OAuth. Rate limit: unknown. Pricing unit: unknown.

HTTP 401, WWW-Authenticate resource_metadata https://mcp.browserstack.com/.well-known/oauth-protected-resource, OAuth metadata lists authorization server https://mcp.browserstack.com

Existing test evidence only. We did not run a new OAuth sign-in or client compatibility test for this card. Claude Code changelog

Score 70/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-11-06 · Server version not reported · Remote endpoint https://mcp.browserstack.com/mcp (streamable-http) · Repo browserstack/mcp-server

Summary: BrowserStack MCP (remote) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake
auth-gated
Tools listed
0
Context cost
Pending The token cost figure is pending. ranking
Login
Needs OAuth sign-in
Tested
2026-11-06

Test results

TestResultPointsEvidence
installpass20Endpoint https://mcp.browserstack.com/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers.
handshakeauth-gated5Auth-gated: HTTP 401 without credentials; OAuth challenge (WWW-Authenticate, resource_metadata https://mcp.browserstack.com/.well-known/oauth-protected-resource). We do not sign in; not counted as working.
maintenancepass25Repo pushed 0 days before test; 154 GitHub stars.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (vendor repo README (github.com/browserstack/mcp-server) via npm package README).
licensepass10AGPL-3.0 (OSI-approved).

Local-model readiness

Not tested

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Tested on 2026-11-06

  • Install from the registry (remote endpoint: connection only)
  • We attempted an MCP initialize with no credentials and got HTTP 401, so we never reached the tool list (Method details: initialize POST answered 401; tools/list not sent)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not checked (remote-only): hosted endpoint, version unknown.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.

Raw test record (JSON)
{
  "name": "browserstack-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-11-06",
  "tools_count": null,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://mcp.browserstack.com/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Auth-gated: HTTP 401 without credentials; OAuth challenge (WWW-Authenticate, resource_metadata https://mcp.browserstack.com/.well-known/oauth-protected-resource). We do not sign in; not counted as working."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 154 GitHub stars."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (vendor repo README (github.com/browserstack/mcp-server) via npm package README)."
    ],
    "license": [
      "pass",
      10,
      "AGPL-3.0 (OSI-approved)."
    ]
  }
}

Install

https://mcp.browserstack.com/mcp

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "browserstack-mcp-remote": {
      "type": "http",
      "url": "https://mcp.browserstack.com/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

Without credentials it said (verbatim): HTTP 401 without credentials; OAuth challenge (WWW-Authenticate, resource_metadata https://mcp.browserstack.com/.well-known/oauth-protected-resource)

  1. Install. No install step: it is a remote server at https://mcp.browserstack.com/mcp.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
  "mcpServers": {
    "browserstack-mcp-remote": {
      "type": "http",
      "url": "https://mcp.browserstack.com/mcp"
    }
  }
}

Not tested with credentials We have not tested this with real credentials.

Test history

Follow this server (RSS) · Monthly changelog

Related: Troubleshooting: 401 Unauthorized on remote servers · MCP servers that need an OAuth sign-in · How to protect AI API keys

FAQ

Is BrowserStack MCP deprecated?

No. browserstack-remote was not deprecated or archived when we last tested it on 2026-11-06.

What replaces BrowserStack MCP?

Nothing; BrowserStack MCP (remote) is not deprecated as of 2026-11-06.

Does BrowserStack MCP need an API key?

Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.

Embed the badge

TestedMCP: 70/100, tested 2026-11-06

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue