Back to MCP Trust Indexm8ven
C
Emerging
74/100
8 days ago

mcp-mssql

A Model Context Protocol server that allows Large Language Models like Claude to execute SQL queries, explore database schemas, and maintain persistent connections to SQL Server databases.

→ JubinSaniei/mcp-mssql· listed on modelscope

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

JubinSaniei

Source: modelscope

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

modelscope

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
2 tools verified — handlers match their declared behaviour
1 read-only tool verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: SQL_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCACHE_TTL_MS
configLOG_LEVELLogging Log level for pino logger (e.g., fatal, error, warn, info, debug, trace, silent). This is read directly from process.env in server.ts, not part of config.js. info
configSQL_ALLOWED_DATABASESenvironment variable to whitelist accessible databases.
configSQL_CONNECTION_TIMEOUTTimeouts & Retries Connection timeout (ms) 30000
configSQL_DATABASEDefault database name to connect to master
configSQL_ENCRYPTSecurity Enable encryption (set to false to disable) true
configSQL_MAX_ROWS
🔐 secretSQL_PASSWORDSQL Server password Required
configSQL_POOL_IDLE_TIMEOUTIdle timeout for connections in pool (ms) 30000
configSQL_POOL_MAXConnection Pool Max connections in pool 10
configSQL_POOL_MINMin connections in pool 0
configSQL_PORTSQL Server port 1433
configSQL_REQUEST_TIMEOUTRequest timeout for queries (ms) 30000
configSQL_RETRY_DELAY_MS
configSQL_RETRY_MAX_DELAY_MS
configSQL_RETRY_MAX_RETRIES
configSQL_SERVERConnection SQL Server hostname or IP localhost
configSQL_TRUST_SERVER_CERTTrust server certificate (set to false to disable) true
configSQL_TRUST_SERVER_CERTIFICATE
configSQL_USERSQL Server username sa
// quality suggestions

All four hints declared on every tool

2/2 tools missing one or more hints — execute_query (missing: idempotentHint); execute_stored_procedure (missing: idempotentHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/2 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/jubinsaniei-mcp-mssql-1ta96q)](https://m8ven.ai/mcp/jubinsaniei-mcp-mssql-1ta96q)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3b7920507904a758c736751ad1e1f6da77043dbd
code hash: 81f5207b433f645c21b076f23893183868f69cde6f908085861136070fb02b00
verified: 8/13/2026, 10:30:44 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client