Skip to content
Agentmart
Submit a tool

Memory Poisoning Scanner

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

Connector by GuardBee · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 1
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/guardbee-memory-poisoning-scanner

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
4 read · 0 write · 0 deleteRead-only
Secrets
None asked for
Install scripts
None found
Runs as
Node.js package

Tools by what they do 4

Read from the source code; the running server may list different tools.

Read 4 · Look things up without changing anything.

  • list_patterns
  • scan_directory
  • scan_file
  • scan_text

Network hosts it talks to 3

  • github.com · found in code
  • guardbee.ai · found in code
  • raw.githubusercontent.com · found in code

Files it touches

  • Any path the agent passes to its tools

Tools (4)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • 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.

Signals

Stars
1
Forks
1
Open issues
14
Weekly downloads
576
Last commit (this folder)
Oct 22, 2026 (6 days ago)
Last release
Oct 22, 2026 (6 days ago)
Last package publish
Oct 22, 2026 (6 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.GuardBee/memory-poisoning-scanner
Version
0.2.2
Auth
No auth
Packages
npm @guardbee/mcp-memory-poisoning-scanner
License
MIT
Repository
github.com/GuardBee/guardbee-mcp
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql

Same server elsewhere

Copies of this server published by others; search shows only one of them.

More from GuardBee

Cite this page

Memory Poisoning Scanner MCP server. Agent Mart. https://agentmart.dev/connectors/guardbee-memory-poisoning-scanner (last updated 2026-10-24)