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 a mobile agent runtime in the Agents and Automation section. It was first seen on 2026-06-30 and last updated 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 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 eggbrid2/mobileClaw a composite score of 7.8 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 'medium' 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
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.