@cevelas/mcp-sqlserver

MCPcommunity
v3.1.0io.github.cvelasquezMITUpdated 5d agonpmGitHub

MCP server for DBAs running dozens of SQL Server instances: grouped connections, plans, indexes

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2GitHub stars
5d agoLast update
Reads these credentials
  • MSSQL_MCP_CONNECTIONS_JSONAPI keyoptional

    The connections JSON inline, for setups that keep credentials out of the filesystem.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.cvelasquez
LicenseMIT
Version3.1.0
Sourcenpm+mcp-registry
npm@cevelas/mcp-sqlserver
GitHubcvelasquez/mcp-sqlserver
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface7 tools · none privileged
Security scan✓ Cleanv3.0.0 · 13d agoHow well does this scan work?
EvalsNone
IndexedSep 10, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · none privileged
Statically extracted from the published packagev3.0.0 · 13d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_connectionsList all available SQL Server connections grouped by connectionGroup

List all available SQL Server connections grouped by connectionGroup

No input schema was published for this tool.

reload_connectionsReload connections from connections.json file without restarting the MCP server. Closes existing connection pools and loads new configuration.

Reload connections from connections.json file without restarting the MCP server. Closes existing connection pools and loads new configuration.

No input schema was published for this tool.

queryExecute a SQL query on the database

Execute a SQL query on the database

No input schema was published for this tool.

get_schemaGet database schema information for specific tables

Get database schema information for specific tables

No input schema was published for this tool.

get_indexesGet index information for a table

Get index information for a table

No input schema was published for this tool.

get_execution_planGet execution plan for a query

Get execution plan for a query

No input schema was published for this tool.

get_stored_procedureGet stored procedure definition

Get stored procedure definition

No input schema was published for this tool.

7 of 7 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for DBAs running dozens of SQL Server instances: grouped connections, plans, indexes

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

7 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-11 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

91 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+79 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in databases