mcp · handle context_engine_2
slimdex · job 80%codegraff · job 81%sverklo · job 81%sanjaya · job 75%mimirs · job 80%code_memory · job 78%atlas_scout_mcp · job 76%lybrary · job 81%narsil_mcp · job 82%LayerMap · job 82%Gus · job 80%Bobbin · job 75%Squiggles · job 79%corbel · job 78%Contour · job 76%agy-lsp · job 76%trace-mcp · job 76%Cortex · job 80%aptu-coder · job 79%Lodesman · job 87%wryneck · job 83%MIMRY · job 83%code-rag-mcp · job 80%repo-graph-mcp · job 77%Bridger · job 81%Delphi Code · job 78%lsp2mcp · job 82%CodeDiver · job 79%Sonarless MCP · job 76%RagPilot · job 79%codescout · job 81%vscode_mcp · job 82%clangaroo · job 78%sense · job 79%agent_lsp · job 76%amdb · job 82%code_context_engine · job 78%Span · job 81%Vera · job 83%codebone · job 77%Sonar · job 80%Sippion · job 79%SCS · job 78%mcpls · job 78%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