# n8n-guard (npm · n8n-guard)

Read-only health checks for self-hosted n8n: datastore growth, stuck runs, retention, git drift.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `n8n-guard`: 69/100 (this document), [markdown](https://verifymcp.io/servers/flow-84-n8n-guard/n8n-guard.md), [page](https://verifymcp.io/servers/flow-84-n8n-guard/n8n-guard)

## Channel facts

- Registry: `npm`
- Package: `n8n-guard`
- Version: `0.1.0`
- 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-11-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 35 of 107 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 75 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 339 tokens (~56/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 n8n-guard MCP server?

n8n-guard runs locally as an npm package, launched with npx -y n8n-guard. 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 flow-84-n8n-guard -- npx -y n8n-guard
```

### Cursor

```json
{
  "mcpServers": {
    "flow-84-n8n-guard": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-guard"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "flow-84-n8n-guard": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-guard"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add flow-84-n8n-guard -- npx -y n8n-guard
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "flow-84-n8n-guard": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "n8n-guard"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add flow-84-n8n-guard --command npx --arg -y --arg n8n-guard
```

### Hermes

```yaml
mcp_servers:
  flow-84-n8n-guard:
    command: "npx"
    args: ["-y", "n8n-guard"]
```

### Netclaw

```json
{
  "McpServers": {
    "flow-84-n8n-guard": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "n8n-guard"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add flow-84-n8n-guard -t stdio -c npx -a -y n8n-guard
```

### Other

```json
{
  "mcpServers": {
    "flow-84-n8n-guard": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-guard"
      ]
    }
  }
}
```

## 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-11-21 (score 69, +4)

- [functional improvement] Stability: unverified → 0.30

### 2026-11-13 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-12 (score 50)

First indexed and scored.

## MCP tools (6)

### `instance_info` (~37 tokens)

Instance info

Reachability, configuration and workflow inventory of the monitored n8n instance. Start here: it shows which checks are configured and which are not.

### `db_health` (~53 tokens)

Database health

Size, per-table breakdown and growth rate of the n8n datastore, plus an estimate of when it hits the critical threshold. Works on SQLite and Postgres. The n8n Public API has no endpoint for this.

### `stuck_executions` (~78 tokens)

Stuck executions

Executions sitting in `running` past a threshold or far past their own workflow's median runtime. Listing by status is not detection: this compares against a baseline.

Input parameters:

- `threshold_minutes` (number): Minutes a run may stay in `running` before it counts as stuck. Defaults to N8N_GUARD_STUCK_MINUTES.

### `retention_report` (~64 tokens)

Retention report

How many execution records are stored, how far back they go, and what pruning to a retention window would free. Read-only: n8n-guard never deletes anything.

Input parameters:

- `keep_days` (number): Retention window to evaluate, in days. Defaults to 30.

### `git_drift` (~44 tokens)

Git drift

Diffs the workflows in the running instance against the JSON exports in a git checkout: live but unexported, exported but deleted, and content that has drifted apart.

### `guard_run` (~63 tokens)

Full guard run

Runs every check in one resilient sweep. Individual steps retry and, if they still fail, are reported as findings while the remaining checks finish. Use this for scheduled monitoring.

Input parameters:

- `keep_days` (number): Retention window used by the retention step. Defaults to 30.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/flow-84-n8n-guard/n8n-guard#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 65
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 50

## Common questions

### What is the n8n-guard MCP server?

n8n-guard is an MCP server listed in the public MCP registry as io.github.flow-84/n8n-guard. Read-only health checks for self-hosted n8n: datastore growth, stuck runs, retention, git drift. This page covers its npm package (n8n-guard).

### Is the n8n-guard MCP server safe to use?

n8n-guard scores 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 n8n-guard MCP server expose?

n8n-guard exposes 6 tools: instance_info, db_health, stuck_executions, retention_report, git_drift, guard_run. Their descriptions and schemas cost roughly 339 tokens of context every time the server is loaded.

### Is the n8n-guard MCP server still maintained?

n8n-guard is still listed as active in the MCP registry. We last reached this channel on 21 November 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 n8n-guard MCP server under?

n8n-guard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the n8n-guard MCP server?

VerifyMCP ran 16 checks on n8n-guard, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/n8n-guard
- Socket report: https://socket.dev/npm/package/n8n-guard
- Repository: https://github.com/flow-84/n8n-guard
- Changelog RSS feed: https://verifymcp.io/servers/flow-84-n8n-guard/n8n-guard.xml
- Changelog JSON feed: https://verifymcp.io/servers/flow-84-n8n-guard/n8n-guard/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/flow-84-n8n-guard/n8n-guard.json
- HTML version of this page: https://verifymcp.io/servers/flow-84-n8n-guard/n8n-guard
