toxic-flow-auditor
io.github.4hmetuyar/toxic-flow-auditor
Finds lethal-trifecta toxic flows in MCP tool catalogs: untrusted input, sensitive data, egress
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.4 · active · updated 2026-10-02 | registry |
| Package | npm: @guardbee/mcp-toxic-flow-auditor | 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-toxic-flow-auditorCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- HeyClaude — Claude & AI workflow directory Search the HeyClaude directory of Claude Code agents, MCP servers, skills, and tools.
- mcp AI-powered design and management for Webflow Sites
- Power Automate MCP Server by Flow Studio Debug, build, and manage Power Automate cloud flows with AI agents
- flowzap Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
- Stack Overflow MCP Server Access Stack Overflow's trusted and verified technical questions and answers.
- 13FLOW Source-linked SEC 13F research, quality checks, watchlists and audit trails for agents.
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/io.github.4hmetuyar/toxic-flow-auditor)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.4hmetuyar/toxic-flow-auditor.