Skip to content
mcp/skillhub

Memory Poisoning Scanner MCP Server

by guardbeeio.github.4hmetuyar/memory-poisoning-scannerv0.1.2

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

1Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active4d ago

Install Memory Poisoning Scanner MCP server

Install in Claude Code

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

Freshness

Active — last maintenance signal 4d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-10-06 · 4d ago · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-09-28 · 11d ago · official registry · v0.1.2

FAQ

›How do I install the Memory Poisoning Scanner MCP server in Claude Code?

Run: claude mcp add memory-poisoning-scanner -- npx -y @guardbee/mcp-memory-poisoning-scanner. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Memory Poisoning Scanner require an API key?

No required environment variables are declared in its published metadata.

›Can I use Memory Poisoning Scanner as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Memory Poisoning Scanner in the official MCP registry?

Yes, as io.github.4hmetuyar/memory-poisoning-scanner.

Alternatives to Memory Poisoning Scanner

Other memory MCP servers.

View all