No release verdicts yet. Scored jobs show how many tools were tested. The rest are not tested.

Queue

MCP2 · measured scores only

Browser Use vs Chrome DevTools MCP

For Let an agent control a browser.

Chrome DevTools MCP scored 89/100 and Browser Use scored 45/100. The gap is 44 points on the rubric. Nothing else is inferred.

Last tested:

Browser Use

45 / 100

Rank 4 on this job · tested 16 Oct 2026

Chrome DevTools MCP

89 / 100

Rank 3 on this job · tested 16 Oct 2026

Rubric breakdown

  • Job result (40)8 Browser Use40 Chrome DevTools MCP
  • Speed and effort (15)4 Browser Use13 Chrome DevTools MCP
  • Price and free tier (15)15 Browser Use15 Chrome DevTools MCP
  • Ease of start (10)5 Browser Use7 Chrome DevTools MCP
  • Reliability and trust (10)5 Browser Use7 Chrome DevTools MCP
  • Community signal (10)8 Browser Use7 Chrome DevTools MCP

Evidence · Browser Use

npm browser-use 0.9.0 (the package calls itself an unofficial TypeScript port) with --provider ollama. It opened http://127.0.0.1:8092/login, then failed: the model does not support multimodal requests. Login, the form, the table, and a screenshot were not completed. Killed at 70s. Evidence: evidence/2026-10-16/batch3/browser-use/task.err.

Evidence · Chrome DevTools MCP

Chrome DevTools MCP 1.11.0 filled the login textboxes, opened /app, listed oak-chest, iron-key, and lantern, saved cdp-form-ok, and returned a 67679-byte screenshot. Evidence: evidence/2026-10-16/batch3/chrome-devtools-mcp/.

Back to Let an agent control a browser · How we rank

Newsletter

The weekly ranking note

One email when a job gets a tested top five, a price changes, or a tool ships something we re-test. No sponsored placements.