mcp · handle repocontext
coding_tools_mcp_2 · job 71%enola · job 72%engineering_audit · job 70%mentu-navigator · job 72%mistle · job 70%nts_mcp_fs · job 76%openclaude · job 71%Repo Context MCP · job 79%sanjaya · job 75%pi-mcp · job 74%leankg · job 74%srag · job 79%speclaw · job 78%srclight · job 75%amdb · job 76%codehelper · job 80%agentmako · job 73%helios · job 75%Context Crafter MCP · job 80%CookieGli · job 80%SpiderBrain · job 73%Koragraph · job 78%FlowCraft · job 74%symvanta · job 75%SecretScan MCP Server · job 72%Agent Env MCP · job 73%Tokenectomy Git · job 71%DeployIt · job 72%code-intel · job 78%git_courer · job 73%morph · job 76%narsil_mcp · job 74%qartez · job 74%mcp_memento · job 77%RepoSage · job 72%revula · job 73%mcp_github_mapper · job 71%slimdex · job 76%CICADA · job 76%agents_remember · job 81%Norma MCP Server · job 73%sift · job 72%sverklo · job 74%Euthynos · job 79%git_mimir · job 74%heeler · 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