mcp · handle turbular_3
MCP Alchemy · job 73%mssql_mcp_server · job 72%turbular · job 83%mssql_mcp_server_2 · job 75%mcpmyadmin · job 73%SQLMesh MCP · job 79%Postgres MCP Server · job 75%mcp-server-rdbms · job 77%ccmcp · job 72%Nile MCP Server · job 76%MCP Toolbox for Databases · job 77%mcp_database_server · job 74%mcp_mysql_server · job 77%db_mcp_2 · job 76%multitool · job 76%DB Explorer MCP · job 76%custom_mcp_servers · job 76%qh · job 73%MCP Server DuckDB · job 75%mcp_server_bigquery · job 79%DB Connector · job 74%Couchbase MCP Server · job 74%mcpg · job 72%Postgres MCP Server · job 76%MCP Oracle · job 78%multi-db-mcp · job 72%pgsteward · job 79%MCP Database Server · job 72%dbmcp · job 74%BigQuery MCP Server · job 82%DemoMcpServer · job 74%mcp_graphql · job 80%mcp_server_mysql · job 77%Free Database MCP Server · job 76%You Design MCP · job 78%Postgres MCP · job 74%postgres2mcp · job 74%scalardb_mcp_server · job 80%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