Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders exploring phone-native agent loops instead of desktop-only automation, but the real-device control surface is broad enough that first evaluation should stay tightly contained.
Who should use it
Who should skip it
Skip eggbrid2/mobileClaw if you cannot isolate its execution environment or audit what data it touches before connecting anything sensitive.
About this signal
eggbrid2/mobileClaw is tracked by RepoRadar as an agent project in the Agents and Automation section. First seen 2026-06-30; the source record was last checked on 2026-06-30. The current verdict is 'worth watch' with a Silver tier and hard setup difficulty. Across RepoRadar's eight signals, eggbrid2/mobileClaw is strongest on workflow potential (8.6) and open-source/build quality (8.4) and weakest on setup ease (4.2) — 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 eggbrid2/mobileClaw record combines a 7.8/10 composite score with separate popularity (1.0), risk (medium), and setup (hard) 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
Runs on real phones with accessibility control, shell execution, and embedded Python, so first evaluation should stay on throwaway devices and non-production accounts; Built-in VPN or proxy controls and dynamic skill creation widen the blast radius beyond a normal mobile QA harness, so policy review belongs before wider rollout.