T

Toxic Flow Auditor

MCP server · by 4hmetuyar

Developer Tools npm v0.1.4

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

View source ↗ More servers

Install

Run one of the commands below, then add the client config underneath.

npmnpx -y @guardbee/mcp-toxic-flow-auditor

Client configuration

Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.

mcpServers{
  "mcpServers": {
    "toxic-flow-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-toxic-flow-auditor"
      ]
    }
  }
}

About this server

Toxic Flow Auditor is listed in the Developer Tools category of the MCPNav directory. It is distributed as npm and can be loaded by any client that speaks the Model Context Protocol.

Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.

Frequently asked questions

What is the Toxic Flow Auditor MCP server?

Toxic Flow Auditor is an MCP server by 4hmetuyar. Finds lethal-trifecta toxic flows in MCP tool catalogs: untrusted input, sensitive data, egress

How do I install Toxic Flow Auditor?

Install it with: npx -y @guardbee/mcp-toxic-flow-auditor. Then add the JSON config to your client's MCP settings and restart the client.

Is Toxic Flow Auditor free to use?

The MCP server itself is free to install. The source is public on https://github.com/GuardBee/guardbee-mcp. Any third-party API it calls (such as a search or maps API) may require its own key and billing.

Which clients support Toxic Flow Auditor?

Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.