nexus-memory (Neboy72/nexus-memory) is an MCP server listed on the M8ven Trust Index. It scores 26 out of 100, grade F. It declares 21 tools. No publisher has claimed this listing.

F
Warning
26/100

nexus-memory

Universal shared memory for AI agents — one brain for all your agents, 100% local & private. Works with Hermes, OpenClaw, Claude Code, Cursor. (Not the PyPI 'nexus-memory' package)

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

Neboy72

Source: Glama · also listed on github_repo_search

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

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
🚨
Secret credentials may flow to a network call
11 flows detected: VOYAGE_API_KEY, JINA_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Reads files from sensitive locations
Touches: ~/.hermes/.env, ~/.hermes/.env, ~/.hermes/.env
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 1 credential: GEMINI_API_KEY
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.
configNEXUS_QDRANT_URL
configNEXUS_REPO_PATH
configNEXUS_ENV_FILE☁️ Voyage: VOYAGE_API_KEY in or MCP env:-block (1024d) — highest recall quality, what we run in production
configNEXUS_QDRANT_HOST
configNEXUS_QDRANT_PORT
configNEXUS_COLLECTION
configNEXUS_TRUST_SWEEP
configNEXUS_RETRIEVAL_WATCH
configNEXUS_AGENT_ID
configNEXUS_QDRANT_COLLECTION
configPYTHONPATHSet PYTHONPATH=/path/to/nexus-memory
configNEXUS_PYTHON
configTAILSCALE_IP
configQDRANT_URL
configNEXUS_EMBEDDING_PROVIDER
configHERMES_HOME
🔐 secretGEMINI_API_KEY
configNEXUS_SKIP_BACKUP_NUDGE
configNEXUS_PREFETCH_CHARSPrefetch slot-replacement race fix + prefetch capacity doubled (10 hits / 2400 chars, NEXUS_PREFETCH_CHARS), hardware auto-entity detection on sync_turn, 71/71 provider tests
configNEXUS_AUTO_ENRICH
configSICA_DEFAULT_RETENTION_DAYS
configSICA_LOW_CONFIDENCEConfigurable: SICA_STALE_TEMP_DAYS, , SICA_MAX_SUGGESTIONS env vars
configSICA_STALE_TEMP_DAYSConfigurable: , SICA_LOW_CONFIDENCE, SICA_MAX_SUGGESTIONS env vars
configSICA_RETENTION_SESSION
configSICA_MAX_SUGGESTIONSConfigurable: SICA_STALE_TEMP_DAYS, SICA_LOW_CONFIDENCE, env vars
configNEXUS_HOST_LABEL
configNEXUS_HF_BGE3Set NEXUS_HF_BGE3=1 — loads bge-m3 directly via sentence-transformers, no Ollama needed (wizard configures this for you)
configNEXUS_AUDIT_INTERVAL
configNEXUS_DEDUP_SWEEPIn-process self-maintenance: dedup sweep (keeper = oldest, JSON backup before every delete, NEXUS_DEDUP_SWEEP=0 kill switch) + selective forgetting + retrieval watch, zero external schedulers
configNEXUS_WEBHOOK_URLSelf-monitoring health audit daemon: in-process thread, 30-day read-only dedup/health audit → ~/.nexus-memory/reports/, health_flags in health tool, optional NEXUS_WEBHOOK_URL push, zero cron dependency, 649 tests
configNEXUS_RERANK
configNEXUS_RERANKER
configNEXUS_RETRIEVAL_START_DELAY
configNEXUS_RETRIEVAL_INTERVAL_SEC
configNEXUS_WATCH_QUERIES
configNEXUS_TRUST_START_DELAY
configNEXUS_TRUST_INTERVAL_SEC
configNEXUS_EMBEDDING_MODEL
configNEXUS_OLLAMA_EMBED_MODEL
configNEXUS_MAX_RECALL
// 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

21/21 tools missing one or more hints — remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); forget (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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.

No access to sensitive paths

Reads sensitive paths: ~/.hermes/.env, ~/.hermes/.env, ~/.hermes/.env

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

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

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/neboy72/nexus-memory?variant=verified)](https://m8ven.ai/mcp/neboy72/nexus-memory)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: a5a060de474f8da3b34b2695406b209fe6746988
code hash: 35fea083f4935a795c17c519072348996fd8ff432c5a42c6f33970799cf71330
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