GoSQLX

io.github.ajitpratap0/gosqlx · v1.16.0 · data-and-databases

GoSQLX is healthy: it completed an MCP handshake in 905 ms and exposes 7 tools.

SQL validation, formatting, parsing, metadata extraction, linting, and security analysis.

Endpoint: https://mcp.gosqlx.dev/mcp (streamable-http)

Facts

Checked (UTC)	Status	Latency	Error
2026-10-22T23:00:14.550Z	Healthy	905

`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.
`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}.
`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 not kept. Returns {formatted_sql, options}.
`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 (traili
`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.
`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.
`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}.