BrowserMCP/mcp
Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
7.2k stars · 588 forks · TypeScript
Avoid
Avoid: no human commits in a year, and most questions go unanswered.
Why
- No human commits since April 2025, and only 0 of 30 recent issues got a maintainer reply. (source 1, source 2, source 3, source 4)
What would change this
- A release or merged commit from a maintainer, or replies to recent issues.
Maintenance
CompleteDormant
- Human commits, 30 days
- 0
- Human commits, 90 days
- 0
- Human commits, 365 days
- 0
- Bot share of commits, 365 days
- 0%
- Last commit
- Apr 24, 2025 (1 year ago)
- Last human commit
- Apr 24, 2025 (1 year ago)
- Authors, 90 days
- 0
- Last release
- none found
- Median PR merge time
- n/a
Responsiveness: of 30 recent issues, 0% got a maintainer reply. Median first response: n/a.
- No human commits in 365 days, and most issues go unanswered.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 6 since Mar 28, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 1
- Contributors
- 1
Top committers
- namuorg: 100% of commits
- No human commits in the last 365 days, so shares use the newest 100 commits back to 2025-03-28T02:01:22Z.
Sources: Commits, Contributors
Stars
CompleteMostly organic, confidence high
Bursts
- Jun 9, 2025 to Jun 9, 2025: about 33 more stars than usual, peak 49 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jun 13, 2025 to Jun 13, 2025: about 64 more stars than usual, peak 80 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jun 18, 2025 to Jun 20, 2025: about 144 more stars than usual, peak 117 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Engagement is low for a repo this size (forks, watchers, issues, contributors).
- 2 stars GitHub has since removed (tracked since Oct 14, 2026).
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- Forks, watchers, issues, and contributors are low for the number of stars.
- Anyone can buy stars for any repo, so this describes the star history only.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- Apache-2.0 (OSI-approved)
- A year ago
- Apache-2.0 (OSI-approved)
Packages
No published packages found.
Sources: GitHub: BrowserMCP/mcp
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/BrowserMCP/mcp)Earlier verdicts
- Oct 14, 2026: Avoid
- Oct 14, 2026: Avoid
Computed 7 hours ago · method 2026.10.2