Memory Poisoning Scanner MCP server

by 4hmetuyar·io.github.4hmetuyar/memory-poisoning-scanner·v0.1.2·1 stars

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

A86/100grade A

What users say

No reviews yet

Safety scan

A86/100

Adoption

Growing

1 stars511 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.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

list_patterns
List every memory-write and memory-readback pattern this scanner detects, grouped by category
scan_directory
Recursively scan a directory of agent source code for memory-poisoning patterns
scan_file
Scan a single file for memory-write and memory-readback poisoning patterns
scan_text
Scan agent code for memory-poisoning risks: untrusted input written into persistent, cross-session memory (MemGPT-style archival/core memory, or a vector store used as a long-term knowledge base) without visible sanitization, and memory retrievals fed into a system/assistant-role message or prompt template as trusted context.

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings

Code scan15 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 0 days ago15/15
Maintainer identitynamespace and repository owner differ4/10

Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

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

🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文

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 (86/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 12 days ago (2026-10-01). The latest release is v0.1.2.
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.

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
Established
C
IWE
Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
not reviewed
Established
A