Skip to content

sqlai.dev SQL Verifier

by JadeSparrow · remote · no sign-in to list tools · v1.0.0 · published by GitHub user JadeSparrow

Executes SQL in a real ephemeral database: rows, typed errors with suggestions, plans, diffs.

Changes · 2
CompareRegistry entry

5 tools: 2 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http sqlai-dev-sql-verifier https://mcp.sqlai.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 2Claude Code: ask
  • run_sqlExecute a SQL query against a fresh ephemeral in-memory database built from your schema (and optional seed rows).No findings

    Why it is in this group

    • The name "run_sql" says "run": a word for a change.
    Description, as the server wrote it
    Execute 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"]].
  • run_sql_batchRun up to 10 queries against the same schema+seed.No findings

    Why it is in this group

    • The name "run_sql_batch" says "run": a word for a change.
    Description, as the server wrote it
    Run 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.
Only reads 3Claude Code: allow
  • diff_resultsAnswer "do these two queries return the same thing?" — the self-check for query refactors.No findings

    Why it is in this group

    • The name "diff_results" says "diff": a word for reading.
    Description, as the server wrote it
    Answer "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).
  • explain_planReturn the engine-native query plan for a query (SQLite: EXPLAIN QUERY PLAN) plus full-table-scan warnings.No findings

    Why it is in this group

    • The name "explain_plan" says "explain": a word for reading.
    Description, as the server wrote it
    Return 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.
  • validate_sqlValidate a SQL query against a schema WITHOUT executing it (parse + name/type binding via EXPLAIN).No findings

    Why it is in this group

    • The name "validate_sql" says "validate": a word for reading.
    Description, as the server wrote it
    Validate 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"?'.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http sqlai-dev-sql-verifier https://mcp.sqlai.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__sqlai-dev-sql-verifier__validate_sql",
      "mcp__sqlai-dev-sql-verifier__explain_plan",
      "mcp__sqlai-dev-sql-verifier__diff_results"
    ],
    "ask": [
      "mcp__sqlai-dev-sql-verifier__run_sql",
      "mcp__sqlai-dev-sql-verifier__run_sql_batch"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as sqlai-dev-sql-verifier. Review it before you use it.