mcp · handle mcp_jira_github_server
mcp_jira_stdio · job 83%Agent Vitals · job 79%Jira MCP Server · job 87%Forgejo MCP · job 79%gitlab_mcp · job 80%Jira MCP · job 79%GitHub Kanban MCP Server · job 78%Traccia · job 79%TaskBounty · job 79%AIO Tests MCP Server · job 79%github_mcp_server · job 81%Atlassian Rovo MCP Server · job 84%Atlassian MCP Server · job 86%mcp_gitlab_server · job 80%llm-wiki · job 78%MCP-github · job 79%deploy_mcp · job 80%Mixedlane · job 76%ctx_5 · job 78%Jira CLI · job 84%gitlab_mr_mcp · job 77%Sandbox APIs MCP · job 79%atlassian_mcp_server · job 77%mcp_server_atlassian_jira · job 88%github-mcp · job 84%mcp_bitbucket · job 84%SYNTARO MCP · job 78%MCP GitHub Tool Eval · job 79%Jira MCP · job 76%BugPilot · job 76%GitHub Developer Assistant MCP Server · job 79%Project Management MCP Server · job 81%Alces for Jira Data Center · job 79%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