Pymssql MCP Server

pymssql-mcp PyPI v0.4.2

Published by bpamiri — 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.

MCP server for Microsoft SQL Server databases

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — 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 1

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([execute_query]) and tools that can send data out ([export_to_json, export_to_csv]) are exposed together. An agent can move private data to the sink.

Evidence: sources [execute_query] → sinks [export_to_json, export_to_csv]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow execute_query → export_to_json

Tools 28

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

  • execute_queryreads sensitive data
  • export_to_csvnetwork egress
  • export_to_jsonnetwork egress
  • begin_transactionno sensitive capability
  • call_stored_procno sensitive capability
  • commit_transactionno sensitive capability
  • connectno sensitive capability
  • delete_knowledgeno sensitive capability
  • delete_rowno sensitive capability
  • describe_stored_procno sensitive capability
Show 18 more tools ↓
  • describe_tableno sensitive capability
  • disconnectno sensitive capability
  • get_all_knowledgeno sensitive capability
  • get_knowledge_topicno sensitive capability
  • get_transaction_statusno sensitive capability
  • insert_rowno sensitive capability
  • list_connectionsno sensitive capability
  • list_databasesno sensitive capability
  • list_knowledgeno sensitive capability
  • list_stored_procsno sensitive capability
  • list_tablesno sensitive capability
  • read_rowsno sensitive capability
  • rollback_transactionno sensitive capability
  • save_knowledgeno sensitive capability
  • search_knowledgeno sensitive capability
  • switch_databaseno sensitive capability
  • update_rowno sensitive capability
  • validate_queryno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v0.4.2 latest A 93/100 1 1.13.0 2026-08-25

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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pymssql-mcp/badge.svg)](https://mcptrustchecker.com/registry/pymssql-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/pymssql-mcp"><img src="https://mcptrustchecker.com/registry/pymssql-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pymssql-mcp/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 pymssql-mcp --online --registry pypi

Use the free API → How scoring works

More in Databases