Memory Poisoning Scanner MCP Server

by 4hmetuyar Your server? Claim it

local only

Memory Poisoning Scanner runs on your own machine — the client starts it, so there is no endpoint to ping. 50 installs a week from npm. Last commit 11 Oct 2026.

Scans agent code for untrusted input poisoning persistent cross-session memory

Installs per day peak 163 · avg 21 · -88% w/w

a month agotoday

Installs / week

npm · @guardbee/mcp-memory-poisoning-scanner

Stars

0 open issues

11 Oct 2026

Last commit

4 releases in 90 days

—

License

TypeScript

Nothing serious here today

Today is the operative word: we check Memory Poisoning Scanner every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add memory-poisoning-scanner -- npx -y @guardbee/mcp-memory-poisoning-scanner

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "memory-poisoning-scanner": {
      "args": [
        "-y",
        "@guardbee/mcp-memory-poisoning-scanner"
      ],
      "command": "npx"
    }
  }
}

~/.codex/config.toml

[mcp_servers.memory-poisoning-scanner]
command = "npx"
args = ["-y", "@guardbee/mcp-memory-poisoning-scanner"]

.cursor/mcp.json

{
  "mcpServers": {
    "memory-poisoning-scanner": {
      "args": [
        "-y",
        "@guardbee/mcp-memory-poisoning-scanner"
      ],
      "command": "npx"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "memory-poisoning-scanner": {
      "args": [
        "-y",
        "@guardbee/mcp-memory-poisoning-scanner"
      ],
      "command": "npx"
    }
  }
}

Alternatives to Memory Poisoning Scanner

same job, measured the same way

Memoize — persistent agent memory

by harrisonford

Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.

answering

Recall

by clauderecall

Persistent memory for Claude Code and Codex. Search and re-inject context from any session.

local only

Recall

by clauderecallhq

Persistent memory for Claude Code. Search, recall, and re-inject context from any session.

186 installs/wk local only

In Memoria

by pi22by7

Persistent codebase intelligence that gives AI assistants memory across sessions

71 installs/wk local only

In Memoria

by pi22by7

Persistent codebase intelligence that gives AI assistants memory across sessions

local only

Repomemory

by danielguru

Persistent memory for AI coding agents. Hybrid search, auto-session capture, context routing.

75 installs/wk local only

Memex

by pragneshbagary

Persistent session memory for Claude Code. Local SQLite, no LLMs, no network.

150 installs/wk local only

Longmem

by marerem

Persistent cross-project memory for Cursor and Claude Code using local semantic search.

83 installs/wk local only

Memory Poisoning Scanner — questions

Answers built from our own checks of this server.

Why is there no uptime for Memory Poisoning Scanner?

Memory Poisoning Scanner runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @guardbee/mcp-memory-poisoning-scanner was installed 50 times last week.

How do I connect Memory Poisoning Scanner?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @guardbee/mcp-memory-poisoning-scanner straight from npm; nothing to host, nothing to sign up for.

How many people use Memory Poisoning Scanner?

The npm package @guardbee/mcp-memory-poisoning-scanner was installed 50 times in the last week. Week over week that is -88%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Memory Poisoning Scanner open source?

We cannot say either way: written in TypeScript and 1 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.