Memory Poisoning Scanner vs Mnemoverse Memory
Memory Poisoning Scanner lists no tools and runs locally and Mnemoverse Memory lists no tools and runs remotely.
| Fact | Memory Poisoning Scannerio.github.GuardBee/memory-poisoning-scanner | Mnemoverse Memoryio.github.mnemoverse/mcp-memory-server |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Local | Remote |
| Needs first | Node.js | – |
| Licence | MIT | MIT |
| Latest version | 0.2.2 | 0.16.0 |
| Known advisories | 0 | 0 |
| Works in | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | 44 | 1,028 |
| Install | Install Memory Poisoning Scanner | Install Mnemoverse Memory |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare Memory Poisoning Scanner with othersCompare Mnemoverse Memory with others