SQL Server MCP
NPM · @CEVELAS/MCP-SQLSERVER
MCP server for DBAs running dozens of SQL Server instances: grouped connections, plans, indexes
Available components
Last scanned (21 hours ago)
Scores higher than 95% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 52 of 161 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to cvelasquez/mcp-sqlserver). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 359 tokens (~51/item across 7 items; 7 tools + 0 resources), lean.Pass
- 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; "query" 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 7 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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 30 Oct 26 +3
- CVE-2026-109461 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 −3
- CVE-2026-109461 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.90 ▲ functional
- 12 Oct 26 −40
- Stability: 0.80 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 3.1.0 → 3.3.0 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 4 Nov 2026 · Analysed npm/@cevelas/mcp-sqlserver@3.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | cvelasquez/mcp-sqlserver |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/cvelasquez/mcp-sqlserver/.github/workflows/publish.yml@refs/tags/v3.3.0 |
| Rekor log index | 3235088667 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:949757d7ac3ef07a7e228ffbb04c66b77e89bd19d3c771bc2193c29ea2e18f503cf59cfdf57a5cb6aac70900928775b4259920726e007c8fddf71ead9 |
Background: How many MCP packages publish verified provenance →
Dependencies 161 packages
| Packages resolved | 161 |
|---|---|
| Stale | 52 |
| 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 →
get_execution_plan ~38
Get execution plan for a query
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | Connection name to use |
| sql | string | yes | SQL query to analyze |
No output schema declared.
No examples provided.
get_indexes ~35
Get index information for a table
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | Connection name to use |
| table | string | yes | Table name |
No output schema declared.
No examples provided.
get_schema ~44
Get database schema information for specific tables
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | Connection name to use |
| table | string | – | Table name (optional, returns all if not specified) |
No output schema declared.
No examples provided.
get_stored_procedure ~37
Get stored procedure definition
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | Connection name to use |
| name | string | yes | Stored procedure name |
No output schema declared.
No examples provided.
list_connections ~19
List all available SQL Server connections grouped by connectionGroup
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query ~156
Execute a SQL query on the database
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | Connection name to use |
| format | string | – | Output format (default json). csv is far more compact for wide or long results: the first line is a JSON header with metadata, then the rows as CSV. |
| maxRows | integer | – | Maximum rows to return across all result sets (default 1000, max 10000). When the cap is hit the query is cancelled on the server and the response starts with truncated: true. A truncated result is i… |
| sql | string | yes | SQL query to execute |
No output schema declared.
No examples provided.
reload_connections ~30
Reload connections from connections.json file without restarting the MCP server. Closes existing connection pools and loads new configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SQL Server MCP server?
SQL Server MCP runs locally as an npm package, launched with npx -y @cevelas/mcp-sqlserver. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @cevelas/mcp-sqlserver
claude mcp add cvelasquez-mcp-sqlserver -- npx -y @cevelas/mcp-sqlserver
What is the SQL Server MCP server?
SQL Server MCP is listed in the public MCP registry as io.github.cvelasquez/mcp-sqlserver. MCP server for DBAs running dozens of SQL Server instances: grouped connections, plans, indexes. This page covers its npm package (@cevelas/mcp-sqlserver).
Is the SQL Server MCP server safe to use?
SQL Server MCP scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 SQL Server MCP server expose?
SQL Server MCP exposes 7 tools: list_connections, reload_connections, query, get_schema, get_indexes, and 2 more. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.
Is the SQL Server MCP server still maintained?
SQL Server MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 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 SQL Server MCP server under?
SQL Server MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.