piia-engram (Patdolitse/piia-engram) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 59 tools. No publisher has claimed this listing.

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

piia-engram

Local-first AI memory you can see, edit, and override — portable across Claude Code, Codex, Cursor, Windsurf, and other MCP coding tools.

→ Patdolitse/piia-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

Patdolitse

Source: Glama · also listed on 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 →

⚡ Connect GitHub for Live Monitored

Install from

GlamaGitHub

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 2 credentials: ENGRAM_AUTH_TOKEN, ENGRAM_SECRET
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.
configENGRAM_TOOLS19 Core (loaded by default) + 40 Advanced (opt-in via ENGRAM_TOOLS=all)
configENGRAM_MCP_STARTUP_SYNC
configENGRAM_HEARTBEAT_INTERVAL
🔐 secretENGRAM_AUTH_TOKEN
configENGRAM_CORS_ORIGINSSet to restrict cross-origin access (e.g. https://your-domain.com).
configMCP_PUBLISHER_PATH
configMCP_PUBLISHER_BIN
configENGRAM_TEST
configENGRAM_DIR
configENGRAM_SBOM_PRIVATE_MARKERS
configENGRAM_LOG_MAX_MB
configENGRAM_BETA_TRACKING
configENGRAM_CALLER_SOURCE
configENGRAM_INITIATION_SOURCE
🔐 secretENGRAM_SECRETFull-disk encryption for all files (v4.0)
configENGRAM_AUDITPer-caller audit (blocked by MCP spec)
configENGRAM_NO_AUTO_BACKUP
configENGRAM_UPGRADE_BACKUP_KEEP
configENGRAM_APPROVAL
configENGRAM_CLIENT_TYPE
configENGRAM_SEARCH
configENGRAM_BACKUP_RETENTION
configENGRAM_GOVERNANCEExports are owner-gated when =1 (see
configENGRAM_CALLER_DEPTH
configENGRAM_CALLER_ROLE
configENGRAM_WORKFLOW_STAGE
configENGRAM_RECONCILE
// 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

59/59 tools missing one or more hints — get_permission_profile (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); manage_caller_trust (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_identity (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +56 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/patdolitse/piia-engram)](https://m8ven.ai/mcp/patdolitse/piia-engram)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 605c22faf4a5fb7eaeb092bf7d9f765f31273629
code hash: 25e6cd0f34df7d2109d58299566991fcd703afa458b5e01d8844bbff7563172d
verified: 9/4/2026, 12:09:23 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