mcp · handle drift
metatron · job 84%mimirs · job 78%Kilo Code · job 79%conxt · job 83%Kilo · job 77%Relay · job 77%GitHub Copilot · job 75%indxr · job 75%mk_family · job 76%relace_mcp · job 75%egc · job 74%mcp_codestyle_server · job 78%ContextStream · job 81%agent_brain · job 74%context_engine · job 75%remembrallmcp · job 78%dotbot · job 77%world_model_mcp · job 77%axon_mcp_server · job 75%codemem · job 78%sprintra · job 84%decisionnode · job 75%graphmemory_ide · job 73%heimdall_mcp_server · job 79%cachly AI Brain · job 81%in_memoria · job 82%context_engineering · job 77%omega_memory · job 71%sync · job 75%mcp_task_orchestrator · job 76%fossil_mcp · job 71%symgraph · job 72%toon_memory · job 77%amdb · job 75%kawacode_mcp · job 78%codemind · job 76%shrimp_task_manager · job 75%mnemex · job 76%linklore · job 73%OpenContext · job 79%AnchorDB · job 76%dmx · 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