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