mcp-sql-console (ManojPabani/mcp-sql-console) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

C
Emerging
74/100

mcp-sql-console

Enables querying Microsoft SQL Server databases using natural language or predefined SQL, with read-only safety. Integrates with Cursor and Claude Desktop for database exploration and management.

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

ManojPabani

Source: Glama

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: DB_PASSWORD, LLM_API_KEY, OPENAI_API_KEY
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.
configCORS_ORIGIN
configDB_CONNECTION_TIMEOUT_MS
configDB_DATABASEDatabase master (set =EmployeeDB to use your app DB)
configDB_ENCRYPT"": "true",
configDB_ODBC_DRIVER
🔐 secretDB_PASSWORDYourStrong!Passw0rd
configDB_POOL_IDLE_TIMEOUT_MS
configDB_POOL_MAX
configDB_POOL_MIN
configDB_REQUEST_TIMEOUT_MS
configDB_SERVER"": "(localdb)\\MSSQLLocalDB",
configDB_TRUST_SERVER_CERTIFICATE"": "true"
configDB_USERFor SQL Authentication fallback, set the DB_USE_WINDOWS_AUTH, , and DB_PASSWORD values in the server environment file.
configDB_USE_WINDOWS_AUTH"": "true",
configHTTP_HOST
configHTTP_PORT
🔐 secretLLM_API_KEY
configLLM_BASE_URL
configLLM_MODELgpt-4o-mini
configNL_ANSWER_CACHE_TTL_MS3. Answer cache (, default 1 min) — identical questions return instantly
configNL_ENGINEEngine selection ( in server/.env):
configNL_PLAN_CACHE_TTL_MS4. SQL plan cache (, default 10 min) — skips NL, re-runs SQL for fresh rows
configNL_SCHEMA_CACHE_TTL_MS2. Schema cache (, default 5 min) + startup warm-up
🔐 secretOPENAI_API_KEY
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

9/9 tools missing one or more hints — sql_health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_predefined_queries (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_predefined_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. 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 4/9 tool handlers declare input schemas (44%)

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

Tool handlers catch errors

Only 0/9 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

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.

Domain consistency

npm scope @mcp-sql-console doesn't match GitHub owner manojpabani

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 7 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/manojpabani/mcp-sql-console)](https://m8ven.ai/mcp/manojpabani/mcp-sql-console)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 42af270d2f2c13fbb475e854053b26bf13a10f27
code hash: 3cd7f7403f8a417b32f5a5c43ccd06dc2b780929cab62c4772d3351ae50c1929
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