Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for agent builders who want a leaner browser-control layer and care about token cost, faster orientation, and fewer round trips during web tasks.
Who should use it
Who should skip it
Skip dondai1234/agent-browser if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
dondai1234/agent-browser is tracked by RepoRadar as a browser mcp server in the AI Automation section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, dondai1234/agent-browser is strongest on workflow potential (9.4) and open-source/build quality (8.4) and weakest on momentum (5.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned dondai1234/agent-browser a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
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
It can act inside logged-in browser sessions, so first evaluation should use a separate browser profile with only the accounts and sites you intend to expose; Automated site actions can still hit CAPTCHAs, rate limits, or unintended form submissions, so keep early runs on test flows and non-production accounts.