mcp · handle digitomancy
mcp_android_server · job 77%Agent Phone Harness · job 77%MobileMCP · job 83%Codex Android Control · job 82%rPlay SDK · job 72%phone-mcp · job 84%Phone for AI · job 81%BenchFleet MCP · job 71%scrcpy_mcp · job 83%Android MCP · job 78%Android Autopilot MCP · job 82%waydroid_mcp · job 83%AutoMobile · job 83%Tasker MCP · job 79%Multi-UIAutomator2 · job 82%jevdevice · job 75%Android Use · job 86%android-adb-mcp · job 87%neuralbridge · job 82%android-lite · job 80%agent_droid_bridge · job 84%ADB MCP Server · job 76%Oh My Android · job 83%airi_android · job 81%Auto Phone · job 85%ios-device-mcp · job 72%Karagöz · job 84%Android ADB MCP Server · job 80%screenhand · job 83%mobilenext_mcp · job 78%android-mcp · job 82%android_mcp · job 79%Android-MCP-go · job 80%DroidBridge · job 85%Mobilerun MCP · job 87%screenpilot · job 71%adbfriend · job 76%ARTEMIS Harness · job 80%android_remote_control_mcp · job 79%deepadb · job 82%mobile-dev-harness · job 76%expo-mcp-bridge · job 75%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