Toxic Flow Auditor MCP server

by 4hmetuyar·io.github.4hmetuyar/toxic-flow-auditor·v0.1.4·1 stars

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

A86/100grade A

What users say

No reviews yet

Safety scan

A86/100

not scanned yet

Adoption

New

1 stars

Reviews

Nobody has reviewed Toxic Flow Auditor yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New registry listings are scanned within a day of import.

Runs npx -y @guardbee/mcp-toxic-flow-auditor on your machine. Read the scan report first; the gateway never runs local packages.

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

From the Toxic Flow Auditor repository's README, as published. We do not edit it. Read it on GitHub

🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文

guardbee.ai — AI Security Copilot for websites.

GuardBee's family of MCP (Model Context Protocol) servers — a single monorepo, independent npm packages.

Nothing above is checked by us. What we check is on the safety report.

Is Toxic Flow Auditor MCP server safe?: Yes, by our scan: it is graded A (86/100). Read the Toxic Flow Auditor safety report
How do I install Toxic Flow Auditor?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Toxic Flow Auditor need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Toxic Flow Auditor maintained?: The last commit was 12 days ago (2026-10-01). The latest release is v0.1.4.