0CompactMem (soolaugust/vMem) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

C
Emerging
74/100
8 days ago

0CompactMem

Zero context compaction for Claude Code & LLM agents. Persistent memory powered by OS primitives (demand paging, kswapd eviction, mlock pinning). Single SQLite file, MCP-native, multi-agent shared.

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

soolaugust

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 →

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.
🔐
You'll be asked for 1 credential: ANTHROPIC_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.
configCLAUDE_PLUGIN_ROOT
configMEMORY_OS_DB
configCLAUDE_SESSION_ID
configMEMORY_OS_DIR
configCLAUDE_SETTINGS_PATH
configCLAUDE_CWD
configEXTRACTOR_POOL_WORKERS
configEXTRACTOR_POOL_POLL
configEXTRACTOR_POOL_BATCH
configMEMORY_OS_OUTPUT_MAX_ACTIVE_CHARS
configMEMORY_OS_OUTPUT_PAGE_CHARS
configMEMORY_OS_OUTPUT_PREVIEW_CHARS
configCLAUDE_TRANSCRIPT_PATH
configCLAUDE_PROJECT
configMEMORY_OS_COMPACT_MARKER_SCAN_BYTES
configMEMORY_OS_TRANSCRIPT_RECLAIM_MAX_STDIO_CHARS
configMEMORY_OS_TRANSCRIPT_RECLAIM_MAX_CONTENT_CHARS
configMEMORY_OS_TRANSCRIPT_RECLAIM_MAX_FIELD_CHARS
configMEMORY_OS_TRANSCRIPT_RECLAIM_MAX_RECORD_CHARS
configMEMORY_OS_HARD_TRANSCRIPT_RECLAIM_TARGET_BYTES
configMEMORY_OS_HARD_TRANSCRIPT_RECLAIM_MIN_TARGET_BYTES
configMEMORY_OS_HARD_TRANSCRIPT_RECLAIM_KEEP_TAIL_LINES
configMEMORY_OS_HARD_TRANSCRIPT_RECLAIM_MAX_LINE_BYTES
configMEMORY_OS_OUTPUT_NOTICE_MAX_CHARS
configMEMORY_OS_DAEMON_SOCK
configMEMORY_OS_DAEMON_IDLE
configMEMORY_OS_DAEMON_MAX_CONN
configCLAUDE_HOOK_EVENT
configANTHROPIC_DEFAULT_SONNET_MODEL
🔐 secretANTHROPIC_API_KEY
configCONTEXT_KERNEL_DIR
configCONTEXT_KERNEL_MAX_OUTPUT_BYTES
configCONTEXT_KERNEL_DEFAULT_READ_LIMIT_LINES
configCONTEXT_KERNEL_GREP_HEAD_LIMIT
configCONTEXT_KERNEL_WARN_BYTES
configCONTEXT_KERNEL_HARD_BYTES
configNET_DB
// 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

8/8 tools missing one or more hints — memory_lookup (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); pin_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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 3 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/soolaugust/vmem)](https://m8ven.ai/mcp/soolaugust/vmem)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1d57f12fbb46742a14ffe623fba474bf554ff954
code hash: 4b99c4e7180e6db3f512d859d5fbe029c2b73a330b72dc22d7aa1abe856328ab
verified: 9/2/2026, 4:49:36 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