GoSQLX
SQL validation, formatting, parsing, metadata extraction, linting, and security analysis.
| Endpoint | https://mcp.gosqlx.dev/mcp (streamable-http) |
|---|---|
| Registry version | 1.17.0 |
| Now | 7 tools · grade C (77) · pin ts_e490f30405e990ad120bdd664d47d9f3 · protocol 2025-06-18 |
| First / last listed | 2026-11-13 00:16 UTC / 2026-11-13 00:16 UTC |
| Grade over time | 2026-11-13: C (77), 7 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: analyze_sql extract_metadata format_sql lint_sql parse_sql security_scan validate_sql
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. params: sql* |
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}. params: sql* |
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}. params: add_semicolon, indent_size, sql*, uppercase_keywords |
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}. params: sql* |
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. params: dialect, sql* |
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. params: sql* |
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}. params: dialect, sql* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.