mcp · handle codediver
sanjaya · job 75%Norma MCP Server · job 77%Corulix · job 81%Flyto2 Runtime · job 79%openclaude · job 75%agentmako · job 82%Agent Env MCP · job 82%Euthynos · job 79%Context Engine · job 79%speclaw · job 81%Agent Review MCP · job 76%bitbucket · job 75%codedebrief · job 76%Needle · job 75%SCS · job 77%code-rag-mcp · job 79%atlas_scout_mcp · job 77%toke_local · job 84%Vera · job 78%MCP GitHub Repository Orchestrator · job 76%mcptask · job 77%Codebase Archaeology MCP · job 77%mcp · job 80%code-intel · job 85%Chronos-Agent · job 74%GitWarren · job 82%Jev Coding Kit · job 75%Open Kioku · job 85%sverklo · job 88%corbel · job 82%wisegit · job 76%Verinoda Symbiosis · job 77%codegraff · job 77%my-pi · job 81%Bobbin · job 75%MCP Repo Auditor · job 79%slimdex · job 79%Pandaone Guard · job 77%wryneck · job 81%ouicu MCP Server · job 77%MCP Project Assistant · job 75%Context Crafter MCP · job 76%ripwire · job 83%MindCtx · job 80%MCP Verified Agent Loop · job 76%pi-coffee · job 78%MCP Repo Tools · job 79%MIMRY · job 82%Repo MCP · job 76%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