SQL Benchmarks Lab
PYPI · SQLBENCHDAG · SCANNED AUG 25
Query pre-computed SQL engine benchmarks. Runs standalone, no server setup required.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security42
- Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
- A known CVE affects paramiko, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- Install-script risk not yet assessed.Unverified
- 18 of 157 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the SQL Benchmarks Lab MCP server?
SQL Benchmarks Lab runs locally as a PyPI package, launched with uvx sqlbenchdag. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sqlbenchdag
claude mcp add rctruta-sqlbenchdag -- uvx sqlbenchdag
{
"mcpServers": {
"rctruta-sqlbenchdag": {
"command": "uvx",
"args": [
"sqlbenchdag"
]
}
}
} {
"servers": {
"rctruta-sqlbenchdag": {
"command": "uvx",
"args": [
"sqlbenchdag"
]
}
}
} codex mcp add rctruta-sqlbenchdag -- uvx sqlbenchdag
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rctruta-sqlbenchdag": {
"type": "local",
"command": [
"uvx",
"sqlbenchdag"
],
"enabled": true
}
}
} openclaw mcp add rctruta-sqlbenchdag --command uvx --arg sqlbenchdag
mcp_servers:
rctruta-sqlbenchdag:
command: "uvx"
args: ["sqlbenchdag"] {
"McpServers": {
"rctruta-sqlbenchdag": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"sqlbenchdag"
]
}
}
} assistant mcp add rctruta-sqlbenchdag -t stdio -c uvx -a sqlbenchdag
{
"mcpServers": {
"rctruta-sqlbenchdag": {
"command": "uvx",
"args": [
"sqlbenchdag"
]
}
}
} 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.
- 13 Aug 26 +1
- Malware scan: unverified → fail ▼ security
- 12 Aug 26 −1
- Malware scan: fail → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- 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
- 10 Aug 26 19
First indexed and scored.
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 25 Aug 2026 · Analysed pypi/sqlbenchdag@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-r374-rxx8-8654 | CVE-2026-44405 | low | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N | no |
| PYSEC-2026-2858 | CVE-2026-44405 | low | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N | no |
Dependencies 157 packages
| Packages resolved | 157 |
|---|---|
| Stale | 17 |
| No linked repository | 1 |
| Tree resolution | Complete |
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.
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the SQL Benchmarks Lab MCP server?
SQL Benchmarks Lab is an MCP server listed in the public MCP registry as io.github.rctruta/sqlbenchdag. Query pre-computed SQL engine benchmarks. Runs standalone, no server setup required. This page covers its PyPI package (sqlbenchdag).
Is the SQL Benchmarks Lab MCP server safe to use?
SQL Benchmarks Lab scores 19 out of 100 on VerifyMCP. A supply-chain scanner flagged a possible malware risk on one channel of this server. We recorded 2 known advisories against it as of 25 August 2026. 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.
Is the SQL Benchmarks Lab MCP server still maintained?
SQL Benchmarks Lab is still listed as active in the MCP registry. We last reached this channel on 25 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.