sqlai.dev SQL Verifier MCP Server

by jadesparrow Your server? Claim it

answering

sqlai.dev SQL Verifier is answering right now. Last checked 8 min ago. It exposes 5 tools.

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

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

213 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check sqlai.dev SQL Verifier every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "sqlai-dev-sql-verifier": {
      "url": "https://mcp.sqlai.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.sqlai-dev-sql-verifier]
url = "https://mcp.sqlai.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "sqlai-dev-sql-verifier": {
      "url": "https://mcp.sqlai.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "sqlai-dev-sql-verifier": {
      "url": "https://mcp.sqlai.dev/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sql

run_sql

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_batch

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.

diff

diff_results

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

explain_plan

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

validate_sql

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"?'.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.sqlai.dev/mcp	streamable-http	answering	271 ms	8 min ago

Alternatives to sqlai.dev SQL Verifier

same job, measured the same way

LINQ to DB

by linq2db

Inspect database schemas and execute SQL queries across multiple database providers with LINQ to DB.

local only

TypeDB

by typedb

Execute TypeQL queries and manage databases and users on a TypeDB server.

local only

Microsoft SQL Server

by alyiox

Read-only-by-default SQL Server: schema, parameterized SELECT, execution plans; writes opt-in.

local only

DBMigratePro Migrations

by provydon

Move a database between providers, or convert MySQL to PostgreSQL, with integrity verified.

answering

Icd10 Coding

by accurecord

ICD-10-CM / HCC medical coding tools with database-verified accuracy and denial-prevention rules.

answering

Max Eats Out

by doubleuson

Editorial guide to restaurants and bars — hand-picked venues with opinions, not a places database

4 tools answering

MCP Schema Designer

by vpatser1

Design database schemas from natural language, validate SQL, generate migrations and types

28 installs/wk local only

PlanetScale

by planetscale

Connect to PlanetScale databases, branches, schema, query insights, and execute SQL

answering

sqlai.dev SQL Verifier — questions

Answers built from our own checks of this server.

What can sqlai.dev SQL Verifier do?

It exposes 5 tools, read directly from the server on our last check. Among them: diff_results, explain_plan, run_sql, run_sql_batch, validate_sql. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is sqlai.dev SQL Verifier working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 213 ms. The bar chart above shows every period we have measured.

How do I connect sqlai.dev SQL Verifier?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does sqlai.dev SQL Verifier need an API key?

No. sqlai.dev SQL Verifier completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is sqlai.dev SQL Verifier?

It answers our handshake in 213 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.