io.github.4hmetuyar/memory-poisoning-scanner
guardbee-memory-poisoning-scanner
Is the io.github.4hmetuyar/memory-poisoning-scanner MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.
Scans agent code for untrusted input poisoning persistent cross-session memory
alive probed 2026-11-15 · unchanged since 2026-10-31
- Run it
- npx -y @guardbee/mcp-memory-poisoning-scanner@0.1.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- guardbee-memory-poisoning-scanner 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 750 tokens in Claude Opus 5.5, exact, measured 2026-10-17. With the Claude Code prefix mcp__…__ on each tool name: 814. The o200k_base estimate is 417. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/GuardBee/guardbee-mcp
- Registry
- active, updated 2026-09-28 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.80×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| scan_directory | 290 | 161 | 39 % |
| scan_text | 245 | 136 | 33 % |
| scan_file | 124 | 69 | 17 % |
| list_patterns | 92 | 51 | 12 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.4hmetuyar/elicitation-auditor · alive
- io.github.4hmetuyar/llm-redteam · alive
- io.github.4hmetuyar/mcp-config-auditor · alive
- io.github.4hmetuyar/mcp-server-auditor · alive
- io.github.4hmetuyar/model-scanner · alive
- io.github.4hmetuyar/oauth-auditor · alive
- io.github.4hmetuyar/prompt-injection-scanner · alive
- io.github.4hmetuyar/prompt-leak-scanner · alive
Servers that mention poisoning.
- Occludra — MCP Gateway (AI Security Gateway) ai.occludra/mcp-gateway · server error
- Execute data-poisoning-detector-mcp io.github.Evozim/data-poisoning-detector-mcp · timeout
- Trust Check io.github.gmahar82-stack/trust-check · alive
- io.github.joeyough/mcpcheck · alive
- MCP Fortress io.github.mcp-fortress/mcp-fortress · not found
- io.github.rezearcher/tech-risk · alive
- MCP Trust & Tool-Poisoning Audit io.github.tylerscomic-lab/mcp-trust-audit-mcp · needs auth
- MCP Security Guard io.github.petrovicistefan/mcp-security-guard · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.