TrueMemory (buildingjoshbetter/TrueMemory) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 11 tools. No publisher has claimed this listing.

B
Emerging
89/100
8 days ago

TrueMemory

The memory your AI should have had from the start. Automatic capture, automatic recall, 100% local. One SQLite file, zero cloud. Works with Claude Code, Claude CLI, Cursor, Codex CLI, Gemini CLI.

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

buildingjoshbetter

Source: github_topic

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 5 credentials: ANTHROPIC_API_KEY, OPENROUTER_API_KEY, OPENAI_API_KEY, GROQ_API_KEY, SUPERMEMORY_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.
configTRUEMEMORY_HOOKS_DIR
configTRUEMEMORY_PYTHON
configTRUEMEMORY_EMBED_MODEL
configTRUEMEMORY_DB_PATH
configTRUEMEMORY_DB
configTRUEMEMORY_DEVICE
🔐 secretANTHROPIC_API_KEY
🔐 secretOPENROUTER_API_KEY
🔐 secretOPENAI_API_KEY
configHF_HUB_OFFLINE
configTRANSFORMERS_OFFLINE
configTRUEMEMORY_PRELOAD_MODELS
configTRUEMEMORY_EXTRACTION
configPYTORCH_MPS_HIGH_WATERMARK_RATIO
configTRUEMEMORY_CUSTOM_ALLOW_DOWNLOAD
configTRUEMEMORY_ENTITY_SHEETS
configTRUEMEMORY_L0_SCORE_SCALE
configTRUEMEMORY_MIN_SALIENCE
configTRUEMEMORY_ALPHA_SURPRISE
configTRUEMEMORY_NO_MODEL_SERVER
configTRUEMEMORY_TELEMETRYAnonymous usage telemetry (tool calls, session counts, platform info) is on by default. We never track memory content, queries, file paths, or API keys. Opt out: export =off
configTRUEMEMORY_CUSTOM_EMBED_MODEL
configTRUEMEMORY_CUSTOM_EMBED_DIM
configTRUEMEMORY_INGEST_SPAWN_CAP
🔐 secretGROQ_API_KEY
configTRUEMEMORY_INSTRUMENTATION
configTRUEMEMORY_INSTRUMENTATION_DB
configOPENAI_BASE_URL
🔐 secretSUPERMEMORY_API_KEY
configTRUEMEMORY_TRANSCRIPT_DIR
configTRUEMEMORY_RECALL_CACHE_TTL
configTRUEMEMORY_RECALL_DEBOUNCE_SECONDS
configTRUEMEMORY_HOOK_RECALL_TIMEOUT
configTRUEMEMORY_USER_ID
configTRUEMEMORY_MAINTENANCE_CHILD
// 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

11/11 tools missing one or more hints — truememory_store (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); truememory_directives (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); truememory_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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/buildingjoshbetter/truememory)](https://m8ven.ai/mcp/buildingjoshbetter/truememory)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 063e5b8844af735a52fde886217a5d26a0f13064
code hash: 54fb9b43d34d598ac1d8b84a6cfbdff30c229ea55dbe43aa3bb86d011da3f5fd
verified: 9/2/2026, 11:32:30 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