memory-poisoning-scanner
io.github.4hmetuyar/memory-poisoning-scanner
Scans agent code for untrusted input poisoning persistent cross-session memory
Description as published in the official MCP registry.
What we measured
| Endpoint | None listed (runs locally) | registry |
|---|---|---|
| GitHub stars | 1 | github.com/GuardBee/guardbee-mcp |
| Last push | 2026-10-02 | GitHub API |
| Registry version | 0.1.2 · active · updated 2026-09-28 | registry |
| Package | npm: @guardbee/mcp-memory-poisoning-scanner | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
npx -y @guardbee/mcp-memory-poisoning-scannerCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Nautilus Compass Memory Local-first long-term memory for AI agents, with byte-recomputable signed verification…
- Synap Memory Persistent memory for AI agents — log and recall conversation context over MCP.
- emem, the verifiable memory protocol for the physical world Shared memory for AI agents. One address per fact, one signature you check. No key to…
- tool-poisoning-scanner Scans MCP tool definitions for hidden instructions and confused-deputy sinks
- BlackVeil DNS & Email Security Scanner DNS and email security scanner with 81 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand…
- basic-memory Local-first knowledge management with bi-directional LLM sync via Markdown files.
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/io.github.4hmetuyar/memory-poisoning-scanner)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.4hmetuyar/memory-poisoning-scanner.