mimer-mcp (mimersql/mimer-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100

mimer-mcp

Enables Mimer SQL database connectivity for browsing schemas, executing read-only queries with parameterization, and managing stored procedures.

→ mimersql/mimer-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

mimersql

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
✅
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 1 credential: DB_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.
configMCP_TRANSPORThttp docker compose up
configMCP_HTTP_HOST
configMCP_HTTP_PORT
configDOTENV_PATH"": "/absolute/path/to/.env"
configDB_USERRequired Database username
🔐 secretDB_PASSWORDRequired Database password
configDB_POOL_INITIAL_CON0 Initial number of idle connections in the pool
configDB_POOL_MAX_UNUSED0 Maximum number of unused connections in the pool
configDB_POOL_MAX_CON0 Maximum number of connections allowed (0 = unlimited)
configDB_POOL_BLOCKfalse Determines behavior when exceeding the maximum number of connections. If true, block and wait for a connection to become available; if false, raise an error when maxconnections is exceeded
configDB_POOL_DEEP_HEALTH_CHECKtrue If true, validates connection health before getting from pool (slower but more reliable)
configMCP_LOG_LEVELINFO Logging level for the MCP server. Options: DEBUG, INFO, WARNING, ERROR, CRITICAL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDB_DSN
// 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

12/12 tools missing one or more hints — list_schemas (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_table_names (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_table_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 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

9/12 tool handlers declare input schemas (75%)

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

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/mimersql/mimer-mcp)](https://m8ven.ai/mcp/mimersql/mimer-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c9fb786ad21ac3389b61f0f72df3df1a35d03761
code hash: d6798265c4c6dce04226f8d45e346ff81080c4132ca45e3e81bc3abed7a11282
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