Engram (rwnalds/engram) is an MCP server listed on the M8ven Trust Index. It scores 48 out of 100, grade D. It declares 32 tools. No publisher has claimed this listing.

D
Caution
48/100

Engram

A self-hosted MCP server that gives AI agents shared, long-term memory over a git-backed folder of markdown, enabling persistent knowledge search, read, and write without a database.

Caution. Specific findings reduced this grade. They are listed on the page. 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

rwnalds

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

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
🚨
Known vulnerabilities in dependencies: 1 critical, 9 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: ANTHROPIC_API_KEY, AUTH_SECRET, GITHUB_CLIENT_SECRET, GOOGLE_CLIENT_SECRET, MCP_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes16 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

brain_schema

READ THIS FIRST, before searching or writing. Returns the vault's SCHEMA.md (folder taxonomy, frontmatter conventions, wikilink model, write protocol) AND a live description of this specific vault: its folders, the `status:` values actually in use, how search ranks notes by authority, and any integr

brain_search
brain_read
brain_list

List every note with metadata (path, title, folder, type, tags, status, authority). Use to discover what exists. `authority` tells you which notes are source-of-truth and which are history.

brain_recent

Notes changed most recently, newest first. Use to catch up on what humans or other agents have done since you last looked.

brain_tree

Return the folder/file tree of the vault.

brain_backlinks

Notes that link to the given note.

brain_graph

The knowledge graph (nodes + edges from wikilinks and related:). Optional folder filter.

brain_write
brain_edit

Overwrite a note. Pass `content` (full raw markdown incl. frontmatter) — read first with brain_read, then write the whole file back. Also accepts `body` (+ optional `frontmatter`) like brain_write.

brain_append

Append text to a note (creates it if missing).

brain_move

Move or rename a note. This is how you retire something: when a note stops being true, move it to an archive folder (see brain_schema → conventions.ranking.archiveFolders) rather than deleting it. Archived notes are demoted in search and excluded by default, so they stop misleading agents while the

brain_create_folder

Create a new folder in the vault (with a .gitkeep).

brain_supersede
brain_capture

Hand over a ROUGH note / brain-dump and let the vault file it. An agent loop reads SCHEMA.md, searches for what already exists, then deliberately creates a new note, appends to a matching one, or archives what this supersedes — and returns a manifest of every path it touched. It reads a note before

brain_delete

Delete a note (recoverable via git history). Prefer brain_move into an archive folder — deleting destroys the reasoning trail, archiving only removes it from search. Delete when the note is wrong or duplicated, archive when it is merely no longer true.

// known CVEs in dependencies1 critical9 high5 medium

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalsimple-git@3.27.0GHSA-r275-fr43-pm7q

simple-git has blockUnsafeOperationsPlugin bypass via case-insensitive protocol.allow config key enables RCE

high@modelcontextprotocol/sdk@1.13.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.13.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.13.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highnext@16.2.7GHSA-6gpp-xcg3-4w24

Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configALLOWED_EMAILS
configALLOWED_GITHUB_LOGINS
🔐 secretANTHROPIC_API_KEY
configAPP_URL
configARCHIVE_FOLDERS
configAUTH_DISABLED
🔐 secretAUTH_SECRET
configCAPTURE_MODEL
configENGRAM_DATA_DIR1. Deploy this repo (root Dockerfile), mount a volume at /data, set =/data.
configENGRAM_GIT_BOOT_DELAY_MS
configENGRAM_STATE_DIR
configGITHUB_CLIENT_ID
🔐 secretGITHUB_CLIENT_SECRET
configGIT_AUTHOR_EMAIL
configGIT_AUTHOR_NAME
configGIT_SYNC_ENABLED
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
configHARNESS_ENABLED
🔐 secretMCP_TOKEN
configVAULT_DIR/path/to/your/obsidian-or-markdown/vault bun dev
configVAULT_IGNORE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_APP_NAME
// 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

32/32 tools missing one or more hints — brain_schema (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); brain_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); brain_read (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +29 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

14/32 tools referenced in tests (44%)

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

Production dependencies are patched

1 critical, 9 high severity in production deps — simple-git@3.27.0 (critical), @modelcontextprotocol/sdk@1.13.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

4/29 production deps abandoned (no release in 2+ years): d3-force@2022-06-14 (4.2y), gray-matter@2023-07-12 (3.1y), rehype-raw@2023-11-20 (2.7y)

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 Verified](https://m8ven.ai/badge/mcp/rwnalds/engram?variant=verified)](https://m8ven.ai/mcp/rwnalds/engram)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 39ddf22ce57a3efad4b797f88e7149f6f6088bf4
code hash: 3b98a5eb9a9967d135804364b159c017eb7589c796d066e6049d33462dc19f61
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