github_mcp_server · job 72%gitlab_mcp_server · job 74%gitintel_mcp · job 76%mcp_workspace · job 73%gitagent_protocol · job 74%mcp_github_mapper · job 71%nts_mcp_fs · job 78%gitea_mcp · job 74%sync_worktrees · job 77%bitbucket · job 77%GitWarren · job 77%MCP GitHub Repository Orchestrator · job 71%coding_tools_mcp_2 · job 71%mcp_gitlab_server · job 77%coding_tools_mcp · job 73%gitmem · job 75%github_mcp_server_3 · job 74%GitOps Safe MCP · job 77%docker_mcp_chatgpt · job 70%deploy_mcp · job 72%RepoContext · job 73%gitlab_mr_mcp · job 72%gitlab_mcp · job 72%github_mapper_mcp_server · job 74%agents_remember · job 76%gitwhy · job 73%github_security_mcp · job 73%Tokenectomy Git · job 73%repo_bridge · job 76%gitmoru · job 78%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