
SQL validation, formatting, parsing, metadata extraction, linting, and security analysis.
Listed on
- Official MCP Registry
- GitHub MCP Registry
- Glamavia MCP Toplist
First seen 6 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
3
Directories
1 via MCP Toplist
7
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
124
GitHub stars
From MCP Toplist
Tools
| Tool | Description | Behaviour |
|---|---|---|
| analyze_sql | Use this when the user wants a complete review of a SQL query. Runs validate, parse, metadata, security, lint, and format concurrently and returns one composite report; hosts that support MCP Apps render it as an interactive report. | Read-only |
| extract_metadata | Use this when the user wants the tables, columns, and functions a SQL query references (e.g. for lineage or impact analysis). Returns {tables, columns, functions}. | Read-only |
| format_sql | Use this when the user wants SQL pretty-printed or reformatted: one clause per line, optional upper-case keywords and trailing semicolon. Comments are preserved; unplaceable optimizer hints are refused. Returns {formatted_sql, options}. | Read-only |
| lint_sql | Use this when the user wants SQL style feedback. Applies the same 10 rules as `gosqlx lint`: L001 trailing whitespace, L002 mixed indentation, L003 consecutive blank lines, L004 indentation depth, L005 line length (>100), L006 column alignment, L007 keyword case (upper), L008 comma placement (trailing), L009 aliasing consistency, L010 redundant whitespace. Returns {violation_count, violations}. | Read-only |
| parse_sql | Use this when the user wants to know how SQL parses: returns an AST summary with the statement count and the type of each statement, optionally for a specific dialect. GO batch separators are excluded from the count. | Read-only |
| security_scan | Use this when the user wants SQL checked for injection patterns: tautologies, UNION attacks, stacked queries, comment bypasses, and more. Returns findings with severity counts. | Read-only |
| validate_sql | Use this when the user wants to know whether a SQL statement is syntactically valid, optionally for a specific dialect. Returns {valid: bool, error?: string, dialect?: string}. | Read-only |