Engram MCP Servers: 10 Implementations Compared

The MCP ecosystem often has several independent packages implementing the same tool — and "Engram" currently has 10. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.

ImplementationPackageTrustCapabilityCoverageFindingsScanned
Engram Source verifiedbest by shuruheel mcp-engram npm A 100/100 Minimal Source 0 2026-07-22
Engram by merrihew engram npm A 100/100 Minimal Source 0 2026-07-22
Engram by danielwhyte engram-mcp npm A 100/100 Minimal Source 0 2026-07-22
Engram by jnmetacode @jnmetacode/engram npm A 100/100 Minimal Source 0 2026-07-22
Engram by hbarefoot @hbarefoot/engram npm A 100/100 High Source 2 2026-07-22
Engram by tinydarkforge @tinydarkforge/engram npm A 100/100 High Source 6 2026-07-22
Engram by PyPI engram PyPI A 98/100 Minimal Source 1 2026-07-22
Engram by cartisien @cartisien/engram-mcp npm A 98/100 Minimal Source 1 2026-07-22
Engram by 199-bio @199-bio/engram npm A 94/100 Minimal Source 1 2026-07-22
Engram by vedtechsolutions @vedtechsolutions/engram-mcp npm A 94/100 Minimal Source 1 2026-07-22

A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.