Memory Poisoning Scanner MCP server

by GuardBee·io.github.GuardBee/memory-poisoning-scanner·v0.3.1·1 stars

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

A91/100grade A

What users say

No reviews yet

Safety scan

A91/100

not scanned yet

Adoption

Growing

1 stars210 downloads/wk

Reviews

Nobody has reviewed Memory Poisoning Scanner yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 91/100; higher than 88% of 4,460 AI and agents servers
GitHub stars: 1; more than 50% of 2,711 AI and agents servers
Downloads a week: 210; more than 75% of 1,538 AI and agents servers with a package

Release history: 3 versions in the registry since 2026-10-13, latest 2026-10-30, typically one every 9 days.

Runs npx -y @guardbee/mcp-memory-poisoning-scanner on your machine. Read the scan report first; the gateway never runs local packages.

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

From the Memory Poisoning Scanner repository's README, as published. We do not edit it. Read it on GitHub

guardbee.ai — AI Security Copilot for websites.

GuardBee's family of MCP (Model Context Protocol) servers — a single monorepo, independent npm packages.

Nothing above is checked by us. What we check is on the safety report.

Is Memory Poisoning Scanner MCP server safe?: Yes, by our scan: it is graded A (91/100). Read the Memory Poisoning Scanner safety report
How do I install Memory Poisoning Scanner?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Memory Poisoning Scanner need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Memory Poisoning Scanner maintained?: The last commit was 22 days ago (2026-10-13). The latest release is v0.3.1.
What can I use instead of Memory Poisoning Scanner?: Servers from other publishers that do the same job: Memanto MCP server, Agent Security Scanner MCP server and Total Agent Memory MCP server. Compare all Memory Poisoning Scanner alternatives.
How does Memory Poisoning Scanner compare with other AI and agents MCP servers?: safety score 91/100 (higher than 88% of 4,460 AI and agents servers); github stars 1 (more than 50% of 2,711 AI and agents servers); downloads a week 210 (more than 75% of 1,538 AI and agents servers with a package). Full comparison.

Same job from other publishers: the closest match first, then the best rated.

Memanto
MCP server for Memanto - persistent semantic memory for any MCP-compatible agent
not reviewed
Established
A
Agent Security Scanner
Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.
not reviewed
Established
C
Total Agent Memory
Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall
not reviewed
Established
A
Basic Memory
Local-first knowledge management with bi-directional LLM sync via Markdown files.
not reviewed
Widely used
B
IWE (iwe.md)
Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
not reviewed
Established
A