M3 Memory (skynetcmd/m3-memory) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 48 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
8 days ago

M3 Memory

Local-first persistent memory layer for MCP agents with hybrid search, file ingestion, and GDPR compliance.

→ skynetcmd/m3-memory· 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

skynetcmd

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

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: NEWS_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 10 credentials: LM_API_TOKEN, LM_STUDIO_API_KEY, AGENT_OS_MASTER_KEY, DD_TOKEN, DD_PASSWORD, GITHUB_TOKEN, GH_TOKEN, M3_LIMIT_PER_PASS, NEWS_API_KEY, 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.
configLM_STUDIO_BASE
configM3_DATABASE
configM3_DASHBOARD_HOST
configM3_DASHBOARD_PORT
configM3_EMBED_SERVER_MAX_BATCH
configM3_EMBED_INTERACTIVE_MAX_TEXTS
configM3_EMBED_SERVER_INTERACTIVE_RESERVED
configM3_EMBED_SERVER_CONCURRENCY
configM3_EMBED_GGUF
configM3_EMBED_SERVER_PORT
configM3_EMBED_SERVER_HOST
🔐 secretLM_API_TOKEN
🔐 secretLM_STUDIO_API_KEY
configM3_OBSERVER_PRECISE_PROVENANCE
configGGML_LOG_LEVEL
configM3_MEMORY_ROOTPayload / repo clone
🔐 secretAGENT_OS_MASTER_KEY
configM3_INSTALL_OXIDATION
configDD_URL
🔐 secretDD_TOKEN
configDD_USERNAME
🔐 secretDD_PASSWORD
configPROCESSOR_ARCHITECTURE
configM3_SKIP_MYPYC
configM3_TASK_LOG_FILE
configM3_LOG_MAX_BYTES
configM3_AGENT_OS_SALT_HEX
configCOMPUTERNAME
configHOSTNAME
configM3_CORE_RS_DISABLE
configM3_ROUTE_SHADOW_MODE
configM3_CHATLOG_DB
configCHATLOG_DB_PATH
configM3_SPILL_MAX_ATTEMPTS
configM3_CHATLOG_DB_PATH
configM3_AUTO_ENRICH
configM3_AUTO_ENRICH_MIN_TURNS
configM3_ENGINE_ROOTDatabases + runtime state (agent_memory.db, agent_chatlog.db, files_database.db)
configM3_CONFIG_ROOTConfiguration (chatlog config, salt)
configM3_FILES_DB_PATH
configFORCE_COLOR
configWT_SESSION
configANSICON
configM3_FIPS_MODEFIPS 140-3 Ready: Standardized encryption pathways allow routing through validated cryptographic modules (e.g., wolfSSL via =1).
configM3_FIPS_STRICT
configM3_LIB_DIR
configM3_WOLFSSL_LIB
configSystemRoot
configM3_WOLFSSL_SHA256
configM3_CRYPTO_BACKEND
configM3_DEBUG_EMBED_MODEL
configM3_DISTILL_AUTO
configNO_COLOR
🔐 secretGITHUB_TOKEN
configM3_STARGAZER
🔐 secretGH_TOKEN
configM3_LLM_URL
configM3_LLM_CONNECT_TIMEOUT
configM3_EMBED_DISCOVERY_NEG_TTL
configM3_GOVERNOR_THROTTLED_LIMIT
configM3_EMBED_URL
configM3_EMBED_MODEL
configM3_CLASSIFY_DEADLINE_S
🔐 secretM3_LIMIT_PER_PASS
configM3_ENRICH_PROFILE
configM3_ENRICH_CONV_LIST
configM3_ENRICH_TRACK_STATE
configM3_ENRICH_MAX_ATTEMPTS
configM3_ENRICH_BUDGET_USD
configM3_ENRICH_INPUT_MAX_K
configM3_ENRICH_MIN_SIZE_K
configM3_ENRICH_MAX_SIZE_K
configM3_ENRICH_SEND_TO
configM3_ENTITY_VOCAB_YAML
configM3_ENTITIES_CONV_LIST
configM3_GLINER_MODEL
configM3_GLINER_THRESHOLD
configM3_GLINER_BATCH_SIZE
configM3_GLINER_DEVICE
configM3_TOOLS_LAZY12.5%
configM3_PATH_BIN
configM3_TRANSPORT
configM3_HTTP_HOST
configM3_HTTP_PORT
configM3_HTTP_PATH
configM3_DISTILL_MODEL
configTERM_PROGRAM
🔐 secretNEWS_API_KEY
configM3_SLM_CLASSIFIER
configM3_SLM_PROFILE
configM3_SLM_PROFILES_DIR
configM3_SQLITE_MMAP_SIZE
configM3_PG_SYNC_TIMEOUT
configM3_SYNC_DBS
configM3_CDW_PG_URL
🔐 secretGEMINI_API_KEY
config_M3_UTF8_REEXEC
configPYTHONUTF8
configM3_AUTO_INSTALL
configM3_MODELS_ROOT
configM3_EMBED_GGUF_AUTODETECT
configM3_EMBED_SERVER_BIN
configM3_NO_MODEL_DOWNLOAD
configM3_DB_BACKENDStable, battle-tested core engine (2,400+ tests) that's safe to build on today; new features and integrations are added actively. SQLite by default; PostgreSQL as a first-class primary backend (M3_DB_BACKEND=postgres) via a pluggable SQL storage seam. (See [features.json](docs/features.json))
configM3_PRIMARY_PG_URL
configPG_URL
configM3_BRIDGE_PATH
// 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

48/48 tools missing one or more hints — log_activity (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_focus (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); retire_focus (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +45 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

24/48 tools referenced in tests (50%)

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

Secrets not logged

1 secret value sent to print

Redact or omit secret values from log output.

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/skynetcmd/m3-memory)](https://m8ven.ai/mcp/skynetcmd/m3-memory)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1e4caaa37685a7b77a99b91bb5090938c8a3ca7c
code hash: 616b427c5c4dfec44c9a6616b67cc57233560cc5a0b5e8bdd84d33907f656ccd
verified: 9/2/2026, 4:50:15 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