MCP server for controlling a real iPhone via macOS iPhone Mirroring...and any MacOs app. Screenshot, tap, swipe, type — from any MCP client.
C-Rank Grade: D (Risky) - 12/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
jfarcand/mirroir-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jfarcand/mirroir-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 12.0 places jfarcand/mirroir-mcp in the D tier.
The external contributor pull request merge rate for jfarcand/mirroir-mcp is 0.0%, based on public PR activity from non-core contributors.
jfarcand/mirroir-mcp does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in jfarcand/mirroir-mcp. Prompt code reviews with positive guidance for new contributors.
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/jfarcand/mirroir-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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Description Could mirroir-mcp support persistent, independently controlled touch contacts for interactions that require holding and dragging in multiple screen regions at the same time? The key requirement is to keep one contact down while moving or tapping with another, and to update or release each contact independently. This would cover simultaneous virtual joystick control, press-and-hold actions, and overlapping drag gestures. From reviewing the current implementation at e1cd98a: InputProviding exposes complete gestures, but no contact IDs or separate touch-down / move / touch-up lifecycle. longPress releases the mouse button after its configured duration. drag interpolates one mouse-left-button trajectory and releases it at the end. This is a feature/feasibility request based on the API and source review; I have not verified this scenario in the game on a real device. Use case PUBG Mobile is a familiar example of the interaction pattern: Keep a contact on the left movement joy
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 jfarcand/mirroir-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 jfarcand/mirroir-mcp acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
jfarcand/mirroir-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 12.0 places jfarcand/mirroir-mcp in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
jfarcand/mirroir-mcp does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for jfarcand/mirroir-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.