sqlai.dev SQL Verifier
REMOTE · MCP.SQLAI.DEV
Executes SQL in a real ephemeral database: rows, typed errors with suggestions, plans, diffs.
Available components
Last scanned (39 minutes ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 838 tokens (~167/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_sql" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Oct 26 +2
- HSTS header: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.sqlai.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sqlai.dev | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c58bd479d8391e1f137bc22311c1c943 |
| SANs: sqlai.dev, mcp.sqlai.dev, *.mcp.sqlai.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.sqlai.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| sqlai.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=86400 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sqlai.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.sqlai.dev/mcp | HTTPS enforced | 301 | https://mcp.sqlai.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
diff_results ~176
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).
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only. |
| query_a | string | yes | Original query. |
| query_b | string | yes | Refactored/alternative query. |
| schema | string | yes | DDL statements. |
| seed | object | – | Optional seed rows: {"table_name": [{"col": value, ...}, ...]}. Max 10MB total. |
No output schema declared.
No examples provided.
explain_plan ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only. |
| query | string | yes | ONE SQL statement to explain. |
| schema | string | yes | DDL statements (include your indexes!). |
No output schema declared.
No examples provided.
run_sql ~224
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"]].
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only. |
| query | string | yes | ONE SQL statement to execute. Stacked statements are rejected. |
| schema | string | yes | DDL statements (CREATE TABLE ...; multiple statements allowed). |
| seed | object | – | Optional seed rows: {"table_name": [{"col": value, ...}, ...]}. Max 10MB total. |
No output schema declared.
No examples provided.
run_sql_batch ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only. |
| queries | array | yes | Up to 10 statements, one per entry. |
| schema | string | yes | DDL statements. |
| seed | object | – | Optional seed rows: {"table_name": [{"col": value, ...}, ...]}. Max 10MB total. |
No output schema declared.
No examples provided.
validate_sql ~151
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"?'.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only. |
| query | string | yes | ONE SQL statement to validate. |
| schema | string | yes | DDL statements. |
No output schema declared.
No examples provided.
How do I install the sqlai.dev SQL Verifier MCP server?
sqlai.dev SQL Verifier is a hosted endpoint at https://mcp.sqlai.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.sqlai.dev
claude mcp add --transport http jadesparrow-sqlai-dev-sql-verifier 'https://mcp.sqlai.dev/mcp'
What is the sqlai.dev SQL Verifier MCP server?
sqlai.dev SQL Verifier is an MCP server listed in the public MCP registry as io.github.JadeSparrow/sqlai-dev-sql-verifier. Executes SQL in a real ephemeral database: rows, typed errors with suggestions, plans, diffs. This page covers its hosted endpoint (https://mcp.sqlai.dev/mcp).
Is the sqlai.dev SQL Verifier MCP server safe to use?
sqlai.dev SQL Verifier scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the sqlai.dev SQL Verifier MCP server expose?
sqlai.dev SQL Verifier exposes 5 tools: run_sql, validate_sql, explain_plan, run_sql_batch, diff_results. Their descriptions and schemas cost roughly 838 tokens of context every time the server is loaded.
Does the sqlai.dev SQL Verifier MCP server require authentication?
No. We connected to sqlai.dev SQL Verifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the sqlai.dev SQL Verifier MCP server still maintained?
sqlai.dev SQL Verifier is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.