A
licenseA
qualityD
maintenanceProvides SQL analysis, linting, and dialect conversion using SQLGlot, enabling validation, transpilation, and extraction of table/column references.
4
32
MIT
GoSQLX
Server Details
SQL validation, formatting, parsing, metadata extraction, linting, and security analysis.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- ajitpratap0/GoSQLX
- GitHub Stars
- 124
- Server Listing
- GoSQLX
- ChatGPT
- –
- Claude
- –
TDQS
A4.1/5.0
Scored across 7 tools
Disambiguation4/5
Each individual tool has a clearly distinct purpose (validate, parse, metadata, security, lint, format). The only overlap is analyze_sql, which aggregates all six others, but its description explicitly frames it as the composite/review entry point, so confusion risk is low.
Naming Consistency4/5
Six tools follow a verb_noun pattern (analyze_sql, extract_metadata, format_sql, lint_sql, parse_sql, validate_sql). security_scan deviates slightly with a noun_verb ordering, but the vocabulary remains predictable and readable.
Tool Count5/5
Seven tools is well-scoped for a SQL analysis toolkit: six focused operations plus one composite review tool, with no filler.
Completeness4/5
The surface covers the full SQL analysis lifecycle: validation, parsing, metadata, security, linting, formatting, and a combined report. Minor gaps exist (e.g., no dialect listing or auto-fix for lint violations), but these are workarounds, not dead ends.
Available Tools
7 toolsanalyze_sqlARead-onlyIdempotentInspect
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.
Inputs: sql (required).
extract_metadataARead-onlyIdempotentInspect
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}.
Inputs: sql (required).
format_sqlARead-onlyIdempotentInspect
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}.
Inputs: sql (required), indent_size, add_semicolon, uppercase_keywords.
lint_sqlARead-onlyIdempotentInspect
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}.
Inputs: sql (required).
parse_sqlARead-onlyIdempotentInspect
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.
Inputs: sql (required), dialect.
security_scanARead-onlyIdempotentInspect
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.
Inputs: sql (required).
validate_sqlARead-onlyIdempotentInspect
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}.
Inputs: sql (required), dialect.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Governed SQL access to your databases: redaction, query review and an audit log.
DBRE-grade SQL analysis inside any MCP client. No connection. No install. Paste a query.
Executes SQL in a real ephemeral database: rows, typed errors with suggestions, plans, diffs.
Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables static, database-free SQL health checks that return rule-based findings and verdicts, propose executable fixes, and verify rewrites are equivalent while comparing execution plans and suggesting indexes. Supports batch/file/git-diff review for CI gating, all at zero-dependency Tier0.MIT
- AlicenseNot gradedqualityBmaintenanceDeterministic SQL static analysis and query-equivalence checking for Postgres, MySQL, SQLite, and SQL Server. Tokenizes locally before forwarding to the API.8Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides SQL parsing, transpilation, formatting, extraction, and condition injection via MCP protocol, enabling agents to validate, analyze, and transform SQL.-
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.