metamcp · job 80%claude_octopus · job 71%google_mcp · job 75%Grok FAF · job 73%deep_dive_mcp · job 75%mcp_compress_router · job 76%mcp_gateway · job 76%mcp_aggregator · job 76%mcp_rest_bridge · job 74%mcp_log_proxy · job 73%mcp_proxy_server · job 85%unla_mcp_gateway · job 71%magg · job 84%forgemax · job 82%custom_mcp_servers · job 79%1mcp_agent · job 78%folio_mcp · job 78%mcpmu · job 83%mcpmanager · job 79%my_cool_proxy · job 81%gridctl · job 75%MCP Gateway · job 76%mcp_proxy · job 77%InterMCP · job 77%mcp-hub · job 73%mcpjungle · job 78%labby · job 76%MoChiPi · job 75%mindbridge_mcp · job 76%CodeMode · job 75%mcp_center · job 75%swarmio · job 75%pi_mcp_adapter · job 72%mcpsense_proxy · job 70%mcp_reticle · job 76%mcp_gateway_3 · job 73%toolport_2 · job 71%mcp_tasks · job 77%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