mcp · handle android_lite
Multi-UIAutomator2 · job 79%Android Use · job 85%android_mcp · job 76%waydroid_mcp · job 78%AutoMobile · job 79%deepadb · job 79%android_remote_control_mcp · job 81%adbfriend · job 72%mcp_android_server · job 73%Agent Phone Harness · job 78%agent_droid_bridge · job 80%ADB MCP Server · job 74%airi_android · job 79%Oh My Android · job 79%screenhand · job 78%android-mcp · job 79%phone-mcp · job 89%ARTEMIS Harness · job 75%Android-MCP-go · job 78%DroidBridge · job 82%Mobilerun MCP · job 85%neuralbridge · job 77%Phone for AI · job 83%icemoon_mcp · job 74%Karagöz · job 80%scrcpy_mcp · job 82%mobilenext_mcp · job 75%Android Autopilot MCP · job 84%Android ADB MCP Server · job 83%Android MCP · job 72%Zeptap · job 73%android-adb-mcp · job 87%MobileMCP · job 79%DroidLens · job 70%Codex Android Control · job 74%Auto Phone · job 81%BenchFleet MCP · job 73%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series