Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

n8n-guard

NPM · N8N-GUARD

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

Available components

+4 this week 69 Trust /100

Last scanned (16 hours ago)

Scores higher than 40% of npm servers

Category Monitoring and Observability

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 35 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 339 tokens (~56/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +4
    • Stability: unverified → 0.30 ▲ functional
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 50

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/n8n-guard@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 107 packages
Packages resolved 107
Stale 35
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~339 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
db_health ~53

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

git_drift ~44

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

guard_run ~63

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.

NameTypeReqDescription
keep_daysnumber–Retention window used by the retention step. Defaults to 30.

No output schema declared.

No examples provided.

instance_info ~37

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

retention_report ~64

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.

NameTypeReqDescription
keep_daysnumber–Retention window to evaluate, in days. Defaults to 30.

No output schema declared.

No examples provided.

stuck_executions ~78

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.

NameTypeReqDescription
threshold_minutesnumber–Minutes a run may stay in `running` before it counts as stuck. Defaults to N8N_GUARD_STUCK_MINUTES.

No output schema declared.

No examples provided.

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.

npm · n8n-guard

# add to Claude Code
claude mcp add flow-84-n8n-guard -- npx -y n8n-guard
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.