Filesystem vs Memory
These two are level on the tashan score (within 1 points), so the score does not decide it. The evidence rows below are where they differ. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| Filesystem | Memory | what it means | |
|---|---|---|---|
| tashan score | 96 | 95 | upkeep + freshness, gated by adoption |
| Adoption evidence | 471k/wk | 95k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 94 | 92 | cadence, maintainers, status |
| Expertise grade | thin | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories | no known advisories | existence of findings is always free; the detail a licence buys is on each dossier |
| Licence | NOASSERTION | NOASSERTION | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
Filesystem
claude mcp add modelcontextprotocol-server-filesystem -- npx -y @modelcontextprotocol/server-filesystemMemory
claude mcp add modelcontextprotocol-server-memory -- npx -y @modelcontextprotocol/server-memoryNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each, including what a licence adds, is on its own page: Filesystem · Memory.