Back to MCP Trust Indexm8ven
F
Warning
21/100
6 days ago

chat-sql

MCP server that enables natural-language SQL queries across multiple databases (ClickHouse, Teradata, PostgreSQL, MySQL, SQL Server, DB2, Oracle, MongoDB) with dialect-correct SQL generation, PII masking, and security-by-construction controls.

→ Umair444/chat-sql-mcp· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. 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

Umair444

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: CHATSQL_BROKER_TOKEN, CHATSQL_CONNECTOR_TOKEN
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.
configCHATSQL_PII_SALTcp .env.example .env # set etc.
configCHATSQL_RAG_DBKEYdelete_query_example (needs a pgvector DB; set ).
configCHATSQL_HOME
configCHATSQL_WHATSAPP_ENABLED
configCHATSQL_EMAIL_ENABLED
configCHATSQL_JUPYTER_ENABLED
configCHATSQL_WIKI_ENABLED
configCHATSQL_DB_CREDS
configCHATSQL_GATEWAY_SOCKET
configCHATSQL_PII_POLICY
configCHATSQL_LEDGER
configCHATSQL_AUDIT_LOG
🔐 secretCHATSQL_BROKER_TOKEN
configCHATSQL_TD_SCRATCH
🔐 secretCHATSQL_CONNECTOR_TOKEN
// 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

32/32 tools missing one or more hints — run_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_query_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); export_to_csv (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +29 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — run_python deletes at line 439 (shutil.rmtree(workdir, ignore_errors=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool test coverage

Only 1/32 tools referenced in tests (3%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

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 5 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 Verified](https://m8ven.ai/badge/mcp/umair444-chat-sql-mcp-ll5zc2?variant=verified)](https://m8ven.ai/mcp/umair444-chat-sql-mcp-ll5zc2)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ac109a8348d8705c14746ecc96391b1937647251
code hash: 477e32631b548e0a9f492496b6c05867814a2bc87699c1d10072a11b2d4de708
verified: 8/13/2026, 7:58:09 AM
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