mcp · handle git_mcp
nyxory · job 75%forgejo-mcp-rs · job 80%Duolo · job 76%repo_bridge · job 88%Gitingest-MCP · job 76%Local Terminal MCP · job 79%witwiki · job 77%my-pi · job 77%gitlab_mcp · job 82%SshWarden · job 76%research-bridge · job 77%Conventional Git · job 74%MCP Repo Tools · job 76%Fusion Jev · job 74%Codebase Guardian · job 74%Kula · job 78%Repo Pulse MCP · job 74%MCP Repo Auditor · job 73%sudocode · job 74%Zoekt MCP Server · job 76%Git MR Reviewer · job 75%Sekura · job 74%deploy_mcp · job 74%mcp_gitlab_server · job 82%Skipper · job 79%MCP GitHub Tool Eval · job 81%Peters ChatGPT MCP Server · job 81%Janus MCP · job 78%CommitLore · job 72%Kudzu · job 83%azdo-mcp · job 74%Codebase Archaeology MCP · job 73%gitintel_mcp · job 74%wspace · job 75%GitVerse Connector · job 75%Repo MCP · job 73%crv-leak-scan · job 74%git_courer · job 74%gitlab-readonly-mcp · job 81%PATLab MCP - Auth Token · job 79%Bitbucket MCP Server · job 75%mcp-repo-context · job 74%EcoScan GitLab MCP Server · job 82%Repo Reader MCP · job 82%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