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

C
Emerging
74/100
5 days ago

mnelo

Local-first knowledge-graph memory layer for AI agents — what Mem0 charges for: 4-way RRF + L2 maintenance + bilingual classifier, one local SQLite. usearch f16 runs it on $10/year VPS.

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

⚡ 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

chinesewebman

Source: Glama · also listed on github_code

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

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: MNELO_AUTH_TOKEN, MNELO_REMOTE_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.
configMNELO_MEMORY_DEBUG
configMNELO_ECHO
configMNELO_MEMORY_DIR
configMNELO_MEMORY_CONFIG
configMNELO_MEMORY_DB_PATH
configMNELO_MEMORY_TIMEZONE
configMNELO_MEMORY_WARM_UP_EMBEDDER
configMNELO_MEMORY_EMBEDDER_MODEL
configMNELO_MEMORY_EMBEDDER_DIM
configMNELO_MEMORY_SERVER_HOST
configMNELO_MEMORY_SERVER_PORT
configMNELO_MEMORY_SERVER_IPFILTER
configMNELO_MEMORY_SERVER_TRUST_XFF
configMNELO_MEMORY_BACKUP_SNAPSHOT_DIR
configMNELO_MEMORY_BACKUP_RETENTION
configMNELO_MEMORY_SEARCH_BACKEND
configMNELO_MEMORY_RECALL_BOOST_KINDS
configMNELO_MEMORY_DIGEST_ENABLED
configMNELO_MEMORY_DIGEST_MAX_CHARS
configMNELO_MEMORY_DIGEST_RECENT_WINDOW_DAYS
configMNELO_MEMORY_DIGEST_IMPORTANCE_THRESHOLD
configMNELO_MEMORY_DIGEST_INJECT_ON_INITIALIZE
configMNELO_MEMORY_TASK_STALE_DAYS_THRESHOLD
configMNELO_MEMORY_CLIENT_TAILSCALE_HOST
configMNELO_MEMORY_LANG
configMNELO_MEMORY_URL
🔐 secretMNELO_AUTH_TOKEN
configMNELO_CI_DB_ROOT
configMNELO_CI_PYTHON
configMNELO_CRON_OUTPUT_DIR
configMNELO_REPO
🔐 secretMNELO_REMOTE_TOKEN
configMNELO_HOME
configMNELO_MEMORY_SSE_URL
// 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

24/24 tools missing one or more hints — memory_remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_relate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +21 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.

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 Score](https://m8ven.ai/badge/mcp/chinesewebman/mnelo)](https://m8ven.ai/mcp/chinesewebman/mnelo)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 67e4875798e7bd6881d2c58c58e8421054f4bd3c
code hash: 3cd7c3e4cc2170776b806c9abc7751d20a411ccd837912650ac7e6c6322af7f3
verified: 9/5/2026, 6:55:27 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