Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want agents to click through a real local app and inspect browser state instead of guessing from server logs or HTML fragments.
Who should use it
Who should skip it
Skip NolanLT/local-browser-mcp if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
NolanLT/local-browser-mcp is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-06-20; the source record was last checked on 2026-06-20. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, NolanLT/local-browser-mcp is strongest on workflow potential (9.8) and open-source/build quality (8.4) and weakest on momentum (3.0) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The NolanLT/local-browser-mcp record combines a 8.3/10 composite score with separate popularity (5.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The server can click, type, run JavaScript, and capture browser state in any host you allow, so keep the allowlist narrow and avoid widening it to accounts or internal apps unless you trust the session boundary.