Mmcp.market

Toxic Flow Auditor MCP server

by GuardBee·io.github.GuardBee/toxic-flow-auditor·v0.1.15·1 stars

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

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

1 stars1.9k downloads/wk

Reviews

Write one

Nobody has reviewed Toxic Flow Auditor yet.

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

Toxic Flow Auditor tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_catalog

    Audit a tools/list-shaped JSON catalog for the lethal trifecta (toxic flow): untrusted content + sensitive/private data + exfiltration or destruction on the same MCP server. Returns an A–F grade.

  • explain_trifecta

    Explain the lethal trifecta / toxic-flow model this auditor uses

  • scan_directory

    Recursively scan a directory of MCP server source for toxic flows across all registered tools

  • scan_file

    Scan a single source file for toxic flows

  • scan_source

    Scan TypeScript/JavaScript MCP server source for .tool(...) registrations and audit them for toxic flows

Public scan report

scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Toxic Flow Auditor in Claude Code, Cursor or VS Code

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
Add to Cursor

What the publisher says

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

guardbee-mcp

🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch

guardbee.ai — AI Security Copilot for websites.

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

Packages

Shortened. The full README is on GitHub.

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

Toxic Flow Auditor: common questions

Is Toxic Flow Auditor MCP server safe?
Yes, by our scan: it is graded A (91/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 2 days ago (2026-10-11). The latest release is v0.1.15.

More from GuardBee →