Chrome DevTools for coding agents
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 63%
Response Time: -
First Timer Success: 54%
ChromeDevTools/chrome-devtools-mcp has a recorded first-timer success rate of 54.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ChromeDevTools/chrome-devtools-mcp respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.7 places ChromeDevTools/chrome-devtools-mcp in the A tier.
The external contributor pull request merge rate for ChromeDevTools/chrome-devtools-mcp is 62.8%, based on public PR activity from non-core contributors.
ChromeDevTools/chrome-devtools-mcp currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Chrome DevTools for coding agents
Balanced & professional review environment in ChromeDevTools/chrome-devtools-mcp. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/ChromeDevTools/chrome-devtools-mcp?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (79% approval). Large PRs (>500 lines) take ~115 hours (28% approval). Keep your diff compact for rapid review.
The exposed evaluate_script schema describes args: Array<string> as 'An optional list of arguments to pass to the function.' It does not say that the strings identify snapshot elements. Passing {pageId:2,function:'(value) => value',args:['literal']} first returned 'No snapshot found for page 2. Use take_snapshot to capture one.' After taking a snapshot, the same call returned 'Element uid "literal" not found on page 2.' The caller expected ordinary function data. Omitting args and serializing the literal into the function source works. Please describe args as snapshot element UIDs, as the (el) => el.innerText example suggests, or provide a separate literal-data channel. This is a schema-description request, not a request to change existing element argument semantics. The same ambiguous description is exposed by our current tools on 2026-10-08 (chrome-devtools-mcp@latest, --isolated --headless). Search found #3015 about a different script schema omission; it does not cover the default a
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to ChromeDevTools/chrome-devtools-mcp, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of ChromeDevTools/chrome-devtools-mcp acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.8% were successfully merged into the primary branch.
ChromeDevTools/chrome-devtools-mcp has a recorded first-timer success rate of 54.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.7 places ChromeDevTools/chrome-devtools-mcp in the Welcoming tier.
The external pull request merge rate is 62.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ChromeDevTools/chrome-devtools-mcp currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ChromeDevTools/chrome-devtools-mcp are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.