# io.github.4hmetuyar/toxic-flow-auditor (npm · @guardbee/mcp-toxic-flow-auditor)

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

- Trust score: 86/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `@guardbee/mcp-toxic-flow-auditor`: 86/100 (this document), [markdown](https://verifymcp.io/servers/4hmetuyar-toxic-flow-auditor/guardbee-mcp-toxic-flow-auditor.md), [page](https://verifymcp.io/servers/4hmetuyar-toxic-flow-auditor/guardbee-mcp-toxic-flow-auditor)

## Channel facts

- Registry: `npm`
- Package: `@guardbee/mcp-toxic-flow-auditor`
- Version: `0.1.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to GuardBee/guardbee-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 226 tokens (~45/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.4hmetuyar/toxic-flow-auditor MCP server?

io.github.4hmetuyar/toxic-flow-auditor runs locally as an npm package, launched with npx -y @guardbee/mcp-toxic-flow-auditor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add 4hmetuyar-toxic-flow-auditor -- npx -y @guardbee/mcp-toxic-flow-auditor
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "4hmetuyar-toxic-flow-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-toxic-flow-auditor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add 4hmetuyar-toxic-flow-auditor -- npx -y @guardbee/mcp-toxic-flow-auditor
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "4hmetuyar-toxic-flow-auditor": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@guardbee/mcp-toxic-flow-auditor"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 4hmetuyar-toxic-flow-auditor --command npx --arg -y --arg @guardbee/mcp-toxic-flow-auditor
```

### Hermes

```yaml
mcp_servers:
  4hmetuyar-toxic-flow-auditor:
    command: "npx"
    args: ["-y", "@guardbee/mcp-toxic-flow-auditor"]
```

### Netclaw

```json
{
  "McpServers": {
    "4hmetuyar-toxic-flow-auditor": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@guardbee/mcp-toxic-flow-auditor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add 4hmetuyar-toxic-flow-auditor -t stdio -c npx -a -y @guardbee/mcp-toxic-flow-auditor
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-11 (score 84, +3)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 37. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-04 (score 80, 0)

- [security improvement] Known CVEs: partial → pass
- [functional] Dependency health: partial → 0.85

### 2026-10-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 79, +11)

- [security regression] Known CVEs: pass → partial
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: GuardBee/guardbee-mcp
- [functional improvement] Stability: unverified → 0.07
- [functional] Dependency health: 0.85 → partial
- [functional] Package version: 0.1.3 → 0.1.4

### 2026-10-01 (score 68, +10)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

## MCP tools (5)

### `audit_catalog` (~85 tokens)

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.

Input parameters:

- `catalog` (string, required): JSON array of tools, or { tools: [...] } from tools/list
- `label` (string): Optional label for the server/catalog

### `scan_source` (~47 tokens)

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

Input parameters:

- `content` (string, required): Source code to scan
- `label` (string)

### `scan_file` (~24 tokens)

Scan a single source file for toxic flows

Input parameters:

- `path` (string, required)

### `scan_directory` (~47 tokens)

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

Input parameters:

- `exclude` (array)
- `maxFiles` (integer)
- `path` (string, required)

### `explain_trifecta` (~23 tokens)

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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/4hmetuyar-toxic-flow-auditor/guardbee-mcp-toxic-flow-auditor#diagnostics

## Score history

- 2026-10-17: 86
- 2026-10-16: 86
- 2026-10-15: 85
- 2026-10-14: 85
- 2026-10-13: 84
- 2026-10-12: 84
- 2026-10-11: 84
- 2026-10-05: 81
- 2026-10-04: 80
- 2026-10-03: 80
- 2026-10-02: 79
- 2026-10-01: 68
- 2026-09-30: 58

## Common questions

### What is the io.github.4hmetuyar/toxic-flow-auditor MCP server?

io.github.4hmetuyar/toxic-flow-auditor is an MCP server listed in the public MCP registry as io.github.4hmetuyar/toxic-flow-auditor. Finds lethal-trifecta toxic flows in MCP tool catalogs: untrusted input, sensitive data, egress. This page covers its npm package (@guardbee/mcp-toxic-flow-auditor).

### Is the io.github.4hmetuyar/toxic-flow-auditor MCP server safe to use?

io.github.4hmetuyar/toxic-flow-auditor scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.4hmetuyar/toxic-flow-auditor MCP server expose?

io.github.4hmetuyar/toxic-flow-auditor exposes 5 tools: audit_catalog, scan_source, scan_file, scan_directory, explain_trifecta. Their descriptions and schemas cost roughly 226 tokens of context every time the server is loaded.

### Is the io.github.4hmetuyar/toxic-flow-auditor MCP server still maintained?

io.github.4hmetuyar/toxic-flow-auditor is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.4hmetuyar/toxic-flow-auditor MCP server under?

io.github.4hmetuyar/toxic-flow-auditor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@guardbee/mcp-toxic-flow-auditor
- Socket report: https://socket.dev/npm/package/@guardbee/mcp-toxic-flow-auditor
- Repository: https://github.com/GuardBee/guardbee-mcp
- Changelog RSS feed: https://verifymcp.io/servers/4hmetuyar-toxic-flow-auditor/guardbee-mcp-toxic-flow-auditor.xml
- Changelog JSON feed: https://verifymcp.io/servers/4hmetuyar-toxic-flow-auditor/guardbee-mcp-toxic-flow-auditor.json
- HTML version of this page: https://verifymcp.io/servers/4hmetuyar-toxic-flow-auditor/guardbee-mcp-toxic-flow-auditor