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

Back to MCP Trust IndexM8ven
B
Emerging
89/100
1 month ago

EngramX

One install. 8 IDEs. Your agent works from a structural map of your repo instead of re-reading whole files — so sessions run longer before the context wall — and bi-temporal mistakes are auto-captured from your git revert history, so it stops repeating fixes that already failed. Context packets run ~50–90% smaller per file (structural size, not a bill saving — run engram bench on yours).

→ NickCirv/engram· 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

NickCirv

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
✅
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 1 credential: ENGRAM_API_TOKEN
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.
configDEMO_FAST
configENGRAM_ALLOWED_ORIGINS
🔐 secretENGRAM_API_TOKEN
configENGRAM_AUTO_REINDEX
configENGRAM_BENCH_PATHREACH
configENGRAM_COMPACT_LEDGER
configENGRAM_DEBUG
configENGRAM_GREP_INTERCEPT0 # don't answer symbol greps from the reference graph
configENGRAM_MCP_CONFIG_PATH
configENGRAM_MISTAKE_GUARD0 # don't warn before an edit that repeats a past mistake
configENGRAM_MISTAKE_GUARD_QUIET
configENGRAM_NO_POSTINSTALL
configENGRAM_NO_UPDATE_CHECKSet =1 to disable the passive "newer version available" hint on every CLI invocation. $CI does the same automatically.
configENGRAM_READ_DEDUP0 # don't dedup same-session re-reads of unchanged files
configENGRAM_SKILLS_DIR
configENGRAM_SUBAGENT_CONTEXT
// 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

6/6 tools missing one or more hints — query_graph (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); god_nodes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); graph_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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

Only 1/6 tools referenced in tests (17%)

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

Shell command execution

22 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

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 5 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/nickcirv/engram)](https://m8ven.ai/mcp/nickcirv/engram)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9fa2a4b74ca8e66560d74d1255c16c43157d32bd
code hash: 290846a4f3c408c362c637fcf8c9e9341ed0ae612d08c260778196064c0f58e3
verified: 8/7/2026, 4:17:31 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