sqlai.dev SQL Verifier MCP server
io.github.JadeSparrow/sqlai-dev-sql-verifierJadeSparrowstreamable-httpv1.0.0Scanned
Executes SQL in a real ephemeral database: rows, typed errors with suggestions, plans, diffs.
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the sqlai.dev SQL Verifier MCP server can do
The sqlai.dev SQL Verifier MCP server is published by the GitHub account JadeSparrow. It has 5 tools. It can create or change data (2 tools: run_sql and run_sql_batch), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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 3Show 3 read-only tools
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.sqlai.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.sqlai.dev/mcp: tools/list returned 5 tools to an anonymous client, including run_sql (write), run_sql_batch (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http sqlai-dev-sql-verifier https://mcp.sqlai.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sqlai-dev-sql-verifier. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.JadeSparrow/sqlai-dev-sql-verifier/verify?hash=2116cdcbb46929ac0a60ad84c5fb7a5602ee5f70da720fa2ae6b6251e0ebdb34" | jq -e '.changed == false'Pinned hash 2116cdcbb469, from Nov 16, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.JadeSparrow/sqlai-dev-sql-verifier/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.JadeSparrow/sqlai-dev-sql-verifier)Source: MCP Registry. Synced Oct 21, 2026, 18:16 UTC.
sqlai.dev SQL Verifier MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the sqlai.dev SQL Verifier MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the sqlai.dev SQL Verifier MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the sqlai.dev SQL Verifier MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the sqlai.dev SQL Verifier MCP server have?
- 5 tools: 2 write, 3 read. run_sql, run_sql_batch, validate_sql, explain_plan and diff_results.
Does the sqlai.dev SQL Verifier MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the sqlai.dev SQL Verifier MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the sqlai.dev SQL Verifier MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.