sqlai.dev SQL Verifier
io.github.JadeSparrow/sqlai-dev-sql-verifierVersion 1.0.0Executes SQL in a real ephemeral database: rows, typed errors with suggestions, plans, diffs.
Status
Responds265 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:38 UTC
- Latency
- 265 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.sqlai.dev/mcpResponds265 msNo sign-in
Claude Code
claude mcp add --transport http sqlai-dev-sql-verifier https://mcp.sqlai.dev/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: sqlai-dev-sql-verifier
Remote MCP server URL: https://mcp.sqlai.dev/mcpCursor
{
"mcpServers": {
"sqlai-dev-sql-verifier": {
"url": "https://mcp.sqlai.dev/mcp"
}
}
}VS Code
code --add-mcp '{"name":"sqlai-dev-sql-verifier","type":"http","url":"https://mcp.sqlai.dev/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
5 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
diff_resultsAnswer "do these two queries return the same thing?" — the self-check for query refactors. Executes query_a and query_b against identical fresh databases and compares result multisets (order-insensitive; order divergence reported separately when ORDER BY is present). Returns equal:boolean, row counts, and capped row-level diffs (only_in_a / only_in_b). | Not declared | Not declared | Not declared | Not declared |
explain_planReturn the engine-native query plan for a query (SQLite: EXPLAIN QUERY PLAN) plus full-table-scan warnings. Use it to check whether an index would be used before recommending one. Example: "SELECT * FROM orders WHERE status=?" on an unindexed column → plan ["SCAN orders"], warning about the full scan. | Not declared | Not declared | Not declared | Not declared |
run_sqlExecute a SQL query against a fresh ephemeral in-memory database built from your schema (and optional seed rows). Returns real rows (max 500, truncation flagged), column names+types, row_count, and dialect notes. Errors come back as structured JSON with type/position/suggestion — a failed query is a useful answer, not a failure of this tool. Example: schema "CREATE TABLE t(id INTEGER, name TEXT);", query "SELECT name FROM t WHERE id=1", seed {"t":[{"id":1,"name":"ada"}]} → rows [["ada"]]. | Not declared | Not declared | Not declared | Not declared |
run_sql_batchRun up to 10 queries against the same schema+seed. Each query executes in its OWN fresh database — writes in one query are NOT visible to the next (use this for testing variants, not for multi-statement transactions). Returns an array of run_sql results in order. | Not declared | Not declared | Not declared | Not declared |
validate_sqlValidate a SQL query against a schema WITHOUT executing it (parse + name/type binding via EXPLAIN). Returns ok with referenced tables, or a structured error: {type: unknown_column|unknown_table|syntax|..., message, position, suggestion}. The suggestion is rule-based (edit distance against your schema). Example: query "SELECT nmae FROM users" → error type unknown_column, suggestion 'did you mean "name"?'. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Repository
- Not given
- Categories (suggested)
- DatabasesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared