m1nd (maxkle1nz/m1nd) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

m1nd

m1nd is a local MCP runtime that gives coding agents graph-native memory of a codebase: structure, docs, decisions, change impact, recovery state, and investigation continuity.

→ maxkle1nz/m1nd· listed on glama

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

maxkle1nz

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.
// 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.
configBASE_PATH
configM1ND_API
configM1ND_MCP_ARGS
configM1ND_MCP_BIN
configM1ND_MCP_BINARY
configM1ND_RELEASE_SMOKE
configM1ND_TEST_COSIGN_PATH
configM1ND_TEST_CRATE_VERSION
configM1ND_TEST_GITHUB_RELEASE_AVAILABLE
configM1ND_TEST_HOME
configM1ND_TEST_NPM_VIEW_JSON
configM1ND_TEST_RELEASE_DIR
configM1ND_TEST_RUNTIME_ABSENT
configM1ND_TEST_RUNTIME_VERSION
configM1ND_TEST_RUNTIME_VERSION_BY_PATH
configM1ND_UPDATE_BACKUP_DIR
configM1ND_UPDATE_SMOKE_DEBUG
configM1ND_UPDATE_STATE_PATH
configM1ND_WORKSPACE_ROOT
configOLDPWD
configPYTHON
configProgramFiles
configSystemRoot
configWINDIR
configM1ND_WORKSPACE
configM1ND_PORT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

8/8 tools missing one or more hints — trust (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); seek (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); predict (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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 test coverage

5/8 tools referenced in tests (63%)

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

Shell command execution

8 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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/maxkle1nz/m1nd)](https://m8ven.ai/mcp/maxkle1nz/m1nd)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 52e6aa7bf627525be3b0661d0ef7296ca8b57fb9
code hash: 248cc5b0b7e82f798df3dfbc642b94974d33b92942551e57b2b35caa64d1fba5
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