sqlai.dev SQL Verifier

REMOTE · MCP.SQLAI.DEV · SCANNED AUG 3

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

Available components

+4 this week 66 66 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security57

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
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
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 Usability69

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.sqlai.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

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

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jadesparrow-sqlai-dev-sql-verifier": {
      "type": "remote",
      "url": "https://mcp.sqlai.dev/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add jadesparrow-sqlai-dev-sql-verifier --url https://mcp.sqlai.dev/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  jadesparrow-sqlai-dev-sql-verifier:
    url: "https://mcp.sqlai.dev/mcp"

// mcp.json

{
  "mcpServers": {
    "jadesparrow-sqlai-dev-sql-verifier": {
      "type": "http",
      "url": "https://mcp.sqlai.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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
26 Jul 26 62

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	6 Jul 2026	4 Oct 2026	ECDSA 256	ECDSA-SHA256	72b1d2a652bad2751343efa57c04d106
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

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

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

MCP tools — 5 exposed · ~838 tokens

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.

Tool Tokens

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).

Input Output Examples

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.

Input Output Examples

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"]].

Input Output Examples

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.

Input Output Examples

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

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	62
27 Jul	62
28 Jul	63
29 Jul	64
30 Jul	64
31 Jul	64
1 Aug	65
2 Aug	65
3 Aug	66