Back to MCP Trust Indexm8ven
69
/ 100
9 days ago
glama

agora-mnemo

mnemo — an MCP server for agent memory with a first-class correction & erasure channel (revert, lineage-aware retraction, tamper-evident deletion receipts). Zero dependencies, 12 tools over stdio

→ DanceNitra/inspeximus· listed on 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.

Install from

Glama

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 6 credentials: LLM_API_KEY, AGORA_API_KEY, OPENAI_API_KEY, MEMOPS_API_KEY, INSPEXIMUS_EMBED_KEY, INSPEXIMUS_LLM_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configADK_FALSIFY
configLLM_BASE_URL
configAGORA_ENV_FILE
configAGORA_API_BASE_URL
🔐 secretLLM_API_KEY
🔐 secretAGORA_API_KEY
configLLM_MODEL
configAGORA_LLM_MODEL_CHEAP
🔐 secretOPENAI_API_KEY
configOPENAI_BASE_URL
configMEMOPS_MEM0_MODEL
configMEMOPS_TOPK
🔐 secretMEMOPS_API_KEY
configGOV_FALSIFY— The audit must be able to fail. =1 skips the erasure, and CI requires the run to
configINSPEXIMUS_NO_UPDATE_CHECK
configINSPEXIMUS_EMBED_HOOKS
configINSPEXIMUS_EMBED_URL— / INSPEXIMUS_EMBED_MODEL / INSPEXIMUS_EMBED_KEY; with none set it uses the lexical
configINSPEXIMUS_EMBED_MODEL— INSPEXIMUS_EMBED_URL / / INSPEXIMUS_EMBED_KEY; with none set it uses the lexical
🔐 secretINSPEXIMUS_EMBED_KEY— INSPEXIMUS_EMBED_URL / INSPEXIMUS_EMBED_MODEL / ; with none set it uses the lexical
configINSPEXIMUS_NOMIC_PREFIX— 0). Omitting them was simply using the model wrong; with prefixes on, our own
configINSPEXIMUS_NO_NUDGE
configINSPEXIMUS_PATH— claude mcp add inspeximus -e =~/.inspeximus_memory.json -- uvx --from "inspeximus[mcp]" inspeximus-mcp
configINSPEXIMUS_REALIGN_MAX
configINSPEXIMUS_LLM_URL
configINSPEXIMUS_LLM_MODEL
🔐 secretINSPEXIMUS_LLM_KEY
configXDG_CONFIG_HOME
configCODEX_HOME
configCLINE_MCP_SETTINGS_PATH
configCLINE_DATA_DIR
configCLINE_DIR
configINSPEXIMUS_ECHO_GUARD— (keyed-without-guard 0.00, a real add-based system 0.57, guard 1.00). Set =0 to disable.
configINSPEXIMUS_MAX_K— hard-capped (, default 50), so a recall drops cheaply into the prompt. Full text is kept by
configINSPEXIMUS_SNIPPET_CHARS
configINSPEXIMUS_READ_RESOLVER
configGITHUB_OUTPUT
configMEM0_LLM
configMEM0_BASE
configN— theater: Source: X and corroborated by are strings a writer controls, so default (distinct source
configLOCOMO_PATH
configLOCOMO_CACHE
configOLLAMA_EMBED_URL
configLOCOMO_OUT
configMEMBENCH_DATA
configTARGET_MODEL
configJUDGE_MODEL
configNBASE
configSTEPS
configSEEDS
configMG_CACHE
configROD_CACHE
configROD_THETA
configE
configRGF_K
configRGF_ALPHA
configSESSION_FALSIFY
configSTORE_FALSIFY
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 6 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/dancenitra-inspeximus-1qud4l)](https://m8ven.ai/mcp/dancenitra-inspeximus-1qud4l)
commit: 3fd8ecd185287e1a3d7a54f52eee142f513c3034
code hash: 02b193109568109bc08830e7ea74b5b4d9a9cbf4550047a95254a1058cac8614
verified: 7/22/2026, 8:48:02 AM
view raw JSON →