PgGuard Agent
Related Servers
Alternatives to PgGuard Agent
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables querying PostgreSQL databases via MCP, with multi-database routing, credential isolation, and truncated results plus full CSV export.-
- AlicenseNot gradedqualityCmaintenanceEnables connecting Postgres databases to MCP clients with built-in query and inspection tools, custom parametrized SQL tools, scoped API keys, group permissions, and audit logging.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to inspect and query PostgreSQL databases through per-endpoint bearer-token authentication, SQL guarding, and comprehensive audit logging, while a web UI manages connections, endpoints, roles, and audit records.MIT
- FlicenseNot gradedqualityCmaintenanceEnables querying and modifying PostgreSQL databases through MCP tools with read/write operations, schema inspection, and write-safety constraints that limit modifications to the mcp schema.1-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to connect directly to PostgreSQL over the wire protocol, explore schemas, tables, and columns, and run parameterized SQL statements. Queries are read-only by default via read-only transactions, with an opt-in write mode and configurable pooling, timeouts, and row caps.MIT
- AlicenseAqualityDmaintenanceEnables secure querying of PostgreSQL databases through MCP-compatible clients. Supports read-only SQL execution, table exploration, and connection management with built-in security validation.364 npm9MIT
TDQS
Scored across 10 tools
Each tool maps to a distinct operation: health check, schema inspection, row queries, DML, DDL, explain, audit, and role/policy lookup. Even though run_select and explain_query both accept queries, their purposes are clearly separated.
Most tools follow a clear verb_noun snake_case convention: list_schemas, list_tables, describe_table, run_select, explain_query, get_audit_tail. Minor deviations are db_health and whoami, which do not follow the verb_noun pattern but remain understandable.
Ten tools is well-scoped for a Postgres guard agent. Each tool serves a necessary purpose in the lifecycle of inspecting and safely modifying a database.
The tool surface covers health, schema discovery, SELECT/DML/DDL execution, query planning, auditing, and policy introspection. Minor gaps like explicit transaction control or listing roles/indexes are not critical, but could make some workflows more seamless.