# GoSQLX

- Registry name: `io.github.ajitpratap0/gosqlx` · version 1.16.0
- Categories (automatic, keyword rules): Databases, Developer tools
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.ajitpratap0%2Fgosqlx
- Server page: https://mcpstation.net/s/io.github.ajitpratap0--gosqlx.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://mcp.gosqlx.dev/mcp`

## Tools (as reported by the server, not verified)

- `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\}.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html