Chrome Agent Bridge · job 74%Public Browser · job 82%nekoro_browser · job 83%ChromeBoost · job 78%Chrome Actuator · job 77%MCP Session Bridge · job 80%Fast Browser MCP · job 79%nuphus_mcp · job 81%SeekBridge · job 81%ruyi_mcp · job 77%MCP Browser Control · job 83%browserjack · job 75%Local Browser MCP · job 82%onday · job 76%BrowserPilot · job 82%Chrome Faithful · job 75%YX Bridge · job 74%browser_bridge_2 · job 80%browser_mcp_2 · job 79%webclaw_2 · job 81%OpenDia · job 77%unbrowser by Unchained · job 76%Xenon Browser · job 81%Jev Browser Sidekick MCP · job 79%Babel Content Clipper · job 76%Browsentic · job 86%Jev Browser Use · job 83%Chrome MCP · job 80%CC Chrome Bridge · job 84%login-mcp · job 77%DSH Codex Chrome · job 86%Browser Use JEV Bridge · job 77%Latch · job 77%G9 Browser Agent · job 84%Latchkey · job 82%Kamurafox · job 73%Chrome Control MCP · job 78%Agent in Chrome · job 78%Browser Buddy · job 76%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