gaussdb-ro-mcp
Related Servers
Alternatives to gaussdb-ro-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceA read-only MCP server that enables AI agents to explore database schemas and execute safe queries on PostgreSQL and MySQL.-
- AlicenseAqualityAmaintenanceA read-only MCP server for exploratory data analysis across PostgreSQL, MySQL, and ClickHouse databases, providing safe, read-only access with comprehensive analysis capabilities.1033 PyPI6MIT
- AlicenseNot gradedqualityCmaintenanceA read-only PostgreSQL MCP server that enables AI agents to perform schema introspection and execute SELECT-only queries. It supports secure database connections through SSL and SSH tunnels while offering a structure-only mode to restrict query access.8 npmMIT
- AlicenseNot gradedqualityBmaintenanceA zero-config, read-only PostgreSQL MCP server that enforces read-only access at the database level using READ ONLY transactions, allowing AI agents to safely explore schemas and run SELECT queries without risk of mutation.11 npmMIT
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for PostgreSQL enabling schema introspection and SELECT queries via MCP clients like Claude, with multi-layered write protection.-
- AlicenseAqualityDmaintenanceA read-only MCP server that enables users to query and explore StarRocks databases through AI assistants like Claude. It supports SQL execution, schema discovery, and secure LDAP authentication for data analysis and metadata exploration.41MIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource or action: listing schemas, listing tables, describing a specific table, executing read-only queries, and testing connectivity. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (describe_table, execute_select, list_schemas, list_tables, test_connection). The naming is uniform and predictable.
With 5 tools, the set is well-scoped for a read-only database exploration server. Each tool earns its place and the count is appropriate for the server's purpose.
The tool surface covers the full read-only workflow: discover schemas, list tables/views, inspect table structure, execute queries, and verify connectivity. No obvious gaps exist for the stated read-only domain.