io.github.deepeshd87/mcp-sql-querystore
PYPI · MCP-SQL-QUERYSTORE
Read-only SQL Server diagnostics for LLM agents: Query Store, waits, plans, indexes
Available components
Last scanned (5 hours ago)
Scores higher than 63% of PyPI servers
Category Databases
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 → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 678 tokens (~113/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Oct 26 +5
- Stability: unverified → 0.33 ▲ functional
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Oct 26 56
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 17 Oct 2026 · Analysed pypi/mcp-sql-querystore@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_parameter_sniffing ~94
Detect queries whose runtime varies widely across multiple compiled plans — the classic parameter-sniffing signature. Ranks by the ratio of slowest to fastest plan mean duration.
| Name | Type | Req | Description |
|---|---|---|---|
| database_name | string | yes | Target SQL Server database name. |
| min_plan_count | integer | – | Minimum distinct plans for a query to be considered (2 = at least two plans). |
| top_n | integer | – | Max rows to return. |
No output schema declared.
No examples provided.
get_missing_index_impact ~92
Aggregate missing-index recommendations found in Query Store plans, ranked by the optimizer's estimated impact score. Groups duplicate recommendations across queries.
| Name | Type | Req | Description |
|---|---|---|---|
| database_name | string | yes | Target SQL Server database name. |
| plan_scan_limit | integer | – | How many recent plans (that contain missing indexes) to scan and aggregate. Higher = more thorough, slower. |
| top_n | integer | – | Max index recommendations to return. |
No output schema declared.
No examples provided.
get_query_execution_plan ~80
Fetch execution plan(s) for a Query Store query_id and return a compact summary (missing indexes, warnings, lookups) plus optional raw XML.
| Name | Type | Req | Description |
|---|---|---|---|
| database_name | string | yes | Target SQL Server database name. |
| include_xml | boolean | – | Include raw showplan XML alongside summary. |
| query_id | integer | yes | Query Store Query ID. |
No output schema declared.
No examples provided.
get_regressed_queries ~155
Detect queries whose performance regressed by comparing a recent period against an earlier baseline period from Query Store.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_hours | integer | – | Length of the baseline window preceding the recent window, in hours (default 7 days). |
| database_name | string | yes | Target SQL Server database name. |
| metric | string | – | Metric to evaluate regression against. |
| min_executions | integer | – | Ignore queries with fewer executions than this in either period (filters noise). |
| recent_hours | integer | – | Length of the recent window, in hours. |
| regression_threshold | number | – | Minimum fractional worsening to flag (0.5 = 50% worse than baseline). |
| top_n | integer | – | Max rows to return. |
No output schema declared.
No examples provided.
get_wait_stats ~90
Aggregate query wait time by wait category over a time window — shows WHY queries are slow (CPU, blocking/locks, IO, memory, etc.) rather than which are slow. Ranked by total wait time.
| Name | Type | Req | Description |
|---|---|---|---|
| database_name | string | yes | Target SQL Server database name. |
| recent_hours | integer | – | Lookback window in hours. |
| top_n | integer | – | Max wait categories to return. |
No output schema declared.
No examples provided.
sweep_regressions ~167
Run regression detection across ALL online databases that have Query Store enabled, and return the worst regressions found per database. Use this to triage a whole instance instead of one database at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_hours | integer | – | Length of the baseline window, in hours. |
| database_names | array | – | Optional explicit list of databases to sweep. If omitted, sweeps all Query Store-enabled online databases. |
| metric | string | – | Metric to evaluate regression against. |
| min_executions | integer | – | Ignore queries below this execution count. |
| recent_hours | integer | – | Length of the recent window, in hours. |
| regression_threshold | number | – | Minimum fractional worsening to flag. |
| top_n_per_db | integer | – | Max regressed queries to return per database. |
No output schema declared.
No examples provided.
How do I install the io.github.deepeshd87/mcp-sql-querystore server?
io.github.deepeshd87/mcp-sql-querystore runs locally as a PyPI package, launched with uvx mcp-sql-querystore. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-sql-querystore
claude mcp add deepeshd87-mcp-sql-querystore -- uvx mcp-sql-querystore
What is the io.github.deepeshd87/mcp-sql-querystore server?
io.github.deepeshd87/mcp-sql-querystore is listed in the public MCP registry as io.github.deepeshd87/mcp-sql-querystore. Read-only SQL Server diagnostics for LLM agents: Query Store, waits, plans, indexes. This page covers its PyPI package (mcp-sql-querystore).
Is the io.github.deepeshd87/mcp-sql-querystore server safe to use?
io.github.deepeshd87/mcp-sql-querystore scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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.
What tools does the io.github.deepeshd87/mcp-sql-querystore server expose?
io.github.deepeshd87/mcp-sql-querystore exposes 6 tools: get_regressed_queries, get_query_execution_plan, analyze_parameter_sniffing, get_missing_index_impact, get_wait_stats, sweep_regressions. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.
Is the io.github.deepeshd87/mcp-sql-querystore server still maintained?
io.github.deepeshd87/mcp-sql-querystore is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.deepeshd87/mcp-sql-querystore server under?
io.github.deepeshd87/mcp-sql-querystore declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.