Sqlserver (tugberkgunver) MCP Server

@tugberkgunver/mcp-sqlserver npm v1.3.2

Published by @tugberkgunver — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A powerful MCP server for SQL Server — schema discovery, query execution, DDL, stored procedures, performance diagnostics & more.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • execute_queryreads sensitive data
  • get_query_planreads sensitive data
  • compare_schemasno sensitive capability
  • describe_procedureno sensitive capability
  • describe_tableno sensitive capability
  • execute_ddlno sensitive capability
  • execute_mutationno sensitive capability
  • execute_procedureno sensitive capability
  • export_queryno sensitive capability
  • generate_codeno sensitive capability
Show 29 more tools ↓
  • generate_er_diagramno sensitive capability
  • generate_insert_scriptsno sensitive capability
  • generate_test_datano sensitive capability
  • get_active_queriesno sensitive capability
  • get_backup_historyno sensitive capability
  • get_blocking_chainsno sensitive capability
  • get_constraintsno sensitive capability
  • get_database_infono sensitive capability
  • get_deadlocksno sensitive capability
  • get_foreign_keysno sensitive capability
  • get_index_usageno sensitive capability
  • get_indexesno sensitive capability
  • get_long_transactionsno sensitive capability
  • get_missing_indexesno sensitive capability
  • get_query_store_statsno sensitive capability
  • get_server_infono sensitive capability
  • get_space_usageno sensitive capability
  • get_table_statsno sensitive capability
  • get_triggersno sensitive capability
  • get_wait_statsno sensitive capability
  • health_checkno sensitive capability
  • list_databasesno sensitive capability
  • list_proceduresno sensitive capability
  • list_schemasno sensitive capability
  • list_serversno sensitive capability
  • list_tablesno sensitive capability
  • list_viewsno sensitive capability
  • rebuild_indexno sensitive capability
  • sample_tableno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.3.2 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/tugberkgunver-mcp-sqlserver/badge.svg)](https://mcptrustchecker.com/registry/tugberkgunver-mcp-sqlserver)
HTML
<a href="https://mcptrustchecker.com/registry/tugberkgunver-mcp-sqlserver"><img src="https://mcptrustchecker.com/registry/tugberkgunver-mcp-sqlserver/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/tugberkgunver-mcp-sqlserver/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @tugberkgunver/mcp-sqlserver --online

Use the free API → How scoring works

Other implementations of Sqlserver 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Databases