SQL Check
Related Servers
Alternatives to SQL Check
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to format SQL, explain queries in plain English, analyze schemas, build queries from natural language, and generate migrations, all without requiring a database connection.529 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to safely query PostgreSQL or SQLite databases read-only through AST-validated guardrails, schema introspection, and statistical table profiling. It returns results as Markdown tables, JSON audit reports, and database health checks.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to explore PostgreSQL schemas, run read-only queries, inspect execution plans, and receive evidence-backed SQL diagnostics with reproducible optimization benchmarks over local stdio.51MIT
- AlicenseNot gradedqualityAmaintenanceDeterministic SQL static analysis and query-equivalence checking for Postgres, MySQL, SQLite, and SQL Server. Tokenizes locally before forwarding to the API.6Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGives AI coding assistants, IDEs, and CI full PostgreSQL schema intelligence from an offline snapshot, enabling linting, query validation, migration safety analysis, and foreign key graph exploration without ever exposing database credentials.35BSD 2-Clause "Simplified"
- AlicenseNot gradedqualityNot gradedmaintenanceAnalyzes SQL queries for performance issues, provides optimization suggestions with automated rewriting, and recommends indexes across multiple database dialects (PostgreSQL, MySQL, Oracle, SQL Server).1MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (validating/running SQL statements against real engines) is unambiguous.
The single name check_sql follows a clear verb_noun convention. No mixed conventions are present since there is only one tool.
A single tool is thin against the typical 3-15 range, though the server's scope (execute and report on SQL) is narrow enough that one entry point is defensible. It packs multiple modes (dialect comparison, max_rows, rollback) into one surface.
For a stateless SQL execution/validation service the core operation is covered, including error reporting, constraints, and dialect comparison. Minor extras like EXPLAIN/plan output or schema-diff tooling are absent but not essential.