Skip to content
mcp/skillhub

Toxic Flow Auditor MCP Server

by guardbeeio.github.4hmetuyar/toxic-flow-auditorv0.1.4

Finds lethal-trifecta toxic flows in MCP tool catalogs: untrusted input, sensitive data, egress

1Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active4d ago

Install Toxic Flow Auditor MCP server

Install in Claude Code

claude mcp add toxic-flow-auditor -- npx -y @guardbee/mcp-toxic-flow-auditor

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-10-02 · 7d ago · official registry · v0.1.4

FAQ

›How do I install the Toxic Flow Auditor MCP server in Claude Code?

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

›Does Toxic Flow Auditor require an API key?

No required environment variables are declared in its published metadata.

›Can I use Toxic Flow Auditor as a remote (hosted) MCP server?

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

›Is Toxic Flow Auditor in the official MCP registry?

Yes, as io.github.4hmetuyar/toxic-flow-auditor.