io.github.NickCirv/engram

MCPcommunity
v4.3.2io.github.NickCirvUnknownUpdated 27d agonpmGitHub

Ranked local code-graph context for AI coding agents. Intercepts reads + greps. Apache-2.0.

Engram makes your AI coding agent stop re-reading the same files — and stop repeating mistakes your repo already fixed. 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.…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
27d agoLast update
Package
Authorio.github.NickCirv
LicenseUnknown
Version4.3.2
Sourcemcp-registry
npmengramx
GitHubNickCirv/engram
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv4.3.2 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Engram makes your AI coding agent stop re-reading the same files — and stop repeating mistakes your repo already fixed. 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…

Keywords
mcp