Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Morous-Dev/engram-cc

NPM · @MOROUS-DEV/ENGRAM-CC · SCANNED AUG 10

Universal AI coding assistant memory — session handoff, SLM compression, and semantic retrieval.

Available components

npm · @morous-dev/engram-cc 32
+3 this week 32 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security77
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects sharp 0.34.5, reached via @huggingface/transformers > sharp. A fixed version is available. View diagnostics → Fail
  • Install-script check failed: the install command fetches or executes arbitrary code (inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
  • 100 of 320 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @morous-dev/engram-cc

# add to Claude Code
claude mcp add morous-dev-engram-cc -- npx -y @morous-dev/engram-cc
# add to Codex CLI
codex mcp add morous-dev-engram-cc -- npx -y @morous-dev/engram-cc
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "morous-dev-engram-cc": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@morous-dev/engram-cc"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add morous-dev-engram-cc --command npx --arg -y --arg @morous-dev/engram-cc
# ~/.hermes/config.yaml
mcp_servers:
  morous-dev-engram-cc:
    command: "npx"
    args: ["-y", "@morous-dev/engram-cc"]
// mcp.json
{
  "mcpServers": {
    "morous-dev-engram-cc": {
      "command": "npx",
      "args": [
        "-y",
        "@morous-dev/engram-cc"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Aug 26 +3
    • Dependency health: partial → 0.86 functional
  • 3 Aug 26 −1

    No change was recorded against any check on this day. Supply Chain Security went from 71 to 68.

  • 2 Aug 26 +10
    • GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
    • Install scripts: unverified → fail ▼ security
    • Provenance: unverified → fail ▼ security
    • Known CVEs: unverified → fail ▼ security
    • The scripts that run when this package is installed changed: postinstall security
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Licence: AGPL-3.0-only functional
  • 1 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Jul 26 −19
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 27 Jul 26 24

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 10 Aug 2026 · Analysed npm/@morous-dev/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Install scripts 1 script
Hook Tier Command
postinstall dangerous node -e "console.log('EngramCC postinstall: skipped automatic setup. Run engramcc inside your project folder to initialize local .engram-cc/.')"
Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-f88m-g3jw-g9cj high yes
Dependencies 320 packages
Packages resolved 320
Deprecated 2
Stale 99
Tree resolution Complete
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.