PreSQL
Related Servers
Alternatives to PreSQL
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnforces safety and governance for SQL queries executed by AI agents, providing read-only enforcement, cost estimation, and audit trails.Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI coding agents to preflight SQL, NoSQL, graph, warehouse, and vector queries against real schemas or pasted DDL, estimating cost/risk, suggesting verified rewrites, and explaining plans before execution. It supports 12 database engines and catches costly query patterns without running the query.9MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to safely inspect and mutate relational databases through AST-level SQL guardrails, isolated dry-run rollback previews, automatic PII masking, and virtual schema hiding. Sensitive mutations are gated behind human sign-off via Slack, Microsoft Teams, or a live web approval feed.1278 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to safely explore and query SQL databases through read-only, AST-checked SQL, database-enforced read-only transactions, timeouts, row caps, PII masking, and audit logging.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and MCP clients to query SQL databases safely through a read-only gateway with AST validation, forced pagination, scoped authorization, and hash-chained audit logging.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query Postgres, BigQuery and DuckDB read-only through policy-checked SQL, with AST-based guards that refuse writes and dangerous functions, column masking on the way out, and an audit log of every query. Also exposes schema browsing and query-planning tools so agents can see allowed tables, columns and costs before running anything.MIT
TDQS
Scored across 3 tools
validate_sql and guard_query overlap heavily: both return a safety verdict (safe/review/blocked vs allow/review/block) with reasons, differing mainly in framing. explain_sql is clearly distinct (no judgment), but an agent could easily struggle to choose between validate and guard.
All three tools follow a clean verb_noun snake_case pattern (validate_sql, explain_sql, guard_query) with no mixing of conventions.
Three tools is well-scoped for a focused SQL safety server, though the overlap between validate_sql and guard_query makes one of them feel somewhat redundant rather than each earning a distinct place.
The domain (pre-execution SQL validation and understanding) is largely covered: validate, explain, and guard. Coverage is adequate, though the surface is thin and could benefit from e.g. schema-aware fix application or batch validation.