mcp · handle dbhub
pgconsole · job 75%haymon_database_mcp · job 76%db_mcp_server · job 76%huangfeng19820712_mcp_mysql_se · job 73%askdb · job 77%mssql_mcp · job 74%DataMCP · job 70%tiger_cli · job 74%smartdb_mcp · job 77%universal_db_mcp · job 73%mcp_workers · job 77%octoquery · job 82%qh · job 79%Database Gateway · job 76%mcp-db-read-only · job 81%postgresql_mcp_server · job 75%tabularis · job 72%pgwarden_mcp · job 75%gresui_web · job 72%db-gateway-mcp · job 74%Postgres MCP Server · job 72%AgentSQL · job 79%MCP DB Hub · job 71%DatabaseMcpServer · job 78%Postgres MCP · job 77%Universal DB MCP · job 83%ariodb · job 77%MCP Database Server · job 82%pgBot · job 78%Postgres MCP · job 78%Portable Database MCP · job 72%Rowbase · job 75%MSSQL MCP Server · job 72%PostgreSQL MCP Server · job 81%MySQL MCP Server · job 72%Devart MCP Server for PostgreSQL · job 75%multi-db-mcp · job 74%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