sqlew (sqlew-io/sqlew) is an MCP server listed on the M8ven Trust Index. It scores 17 out of 100, grade F. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
17/100

sqlew

Stores architectural decisions in a SQL database for persistent AI agent memory, enabling cross-session continuity and duplicate detection.

→ sqlew-io/sqlew· 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

⚡ 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

sqlew-io

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

Glamanot scored here

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
🚨
Reads files from sensitive locations
Touches: /.dockerenv
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: MYSQL_PASSWORD, PG_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high2 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.25.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

highmysql2@3.15.3GHSA-3f6p-5ww8-9rcr

MySQL2: Auth Plugin Downgrade to mysql_clear_password Leaks Plaintext Credentials

lowmysql2@3.15.3GHSA-rgwj-5xj2-c3m3

MySQL2: Unbounded zlib inflate in compressed MySQL protocol handler allows decompression-bomb DoS

lowsmol-toml@1.4.2GHSA-v3rj-xjv7-4jmq

smol-toml: Denial of Service via TOML documents containing thousands of consecutive commented lines

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configMYSQL_DATABASE
configMYSQL_HOST
🔐 secretMYSQL_PASSWORD
configMYSQL_PORT
configMYSQL_USER
configPG_DATABASE
configPG_HOST
🔐 secretPG_PASSWORD
configPG_PORT
configPG_USER
configSQLEW_DB_PATH
configSQLEW_DEBUG
configXDG_DATA_HOME
// quality suggestions

No access to sensitive paths

Reads sensitive paths: /.dockerenv

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Production dependencies are patched

0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.25.3 (high), mysql2@3.15.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/9 production deps stale: knex-schema-inspector@2023-10-25 (2.9y)

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 2 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/sqlew-io/sqlew?variant=verified)](https://m8ven.ai/mcp/sqlew-io/sqlew)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 68c34298c130e3afd917b30b108d8448d979c308
code hash: 74eb39dc665c8d6e24081d484826540b83f46e89de15dc5bcf28ae0251c004ab
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