mcp · handle feinman
RepoSage · job 81%mcp_github_mapper · job 75%slimdex · job 80%Jevex · job 78%whichlib · job 74%sverklo · job 75%painpoints · job 74%orangepro_mcp · job 77%Context Crafter MCP · job 78%wheel-hub · job 79%ripwire · job 88%mentu-navigator · job 75%RepoContext · job 76%LayerMap · job 81%Corulix · job 81%Noulette · job 76%Codebase Archaeology MCP · job 76%cc-code-review · job 74%Architect Anything · job 81%grasp · job 76%CodeScope · job 80%DSH Strong Skills · job 73%CodeDiver · job 80%Ripplet · job 77%codenib · job 77%corbel · job 76%agentmako · job 80%Norma MCP Server · job 75%Mezura · job 76%github_mapper_mcp_server · job 77%mcp_adr_analysis_server · job 76%Ripple · job 76%ArchitectureGraph · job 77%RepoImpact · job 74%ContribOS · job 76%gitintel_mcp · job 76%code-intel · job 88%pi-coffee · job 77%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