N8n
NPM · @PIPEWORX/MCP-N8N · 2 COMPONENTS
n8n MCP — query your own n8n instance (BYO).
Available components
Last scanned (1 hour ago)
Scores higher than 73% of npm servers
Category Workflow Automation
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-n8n). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 746 tokens (~248/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-n8n@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-n8n |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-n8n/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655599882 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e1734802c2f71b8eacd89530f99735821f881685679501000e1d7260c90000c2ec05af314a2a872006646c42c9ec620f0069f69837a8fef64d27d30fc |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
n8n_get_workflow ~195
Get one workflow's detail by id from your n8n instance — name, active state, node list (which integrations it uses), tags, timestamps. Get the id from n8n_list_workflows. Requires your instance_url + n8n API key (_apiKey).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | REQUIRED — your n8n API key (Settings → n8n API → Create an API key). Sent as the X-N8N-API-KEY header. No shared key exists for this pack. |
| instance_url | string | yes | REQUIRED — your n8n instance base URL, e.g. "https://you.app.n8n.cloud" (n8n Cloud) or "https://n8n.example.com" (self-hosted). Must be a public https URL. |
| workflow_id | string | yes | The workflow id — from n8n_list_workflows. |
No output schema declared.
No examples provided.
n8n_list_executions ~251
List recent workflow executions (runs) in your n8n instance — for "did our workflows run", "show recent failures", "execution history". Each: id, workflowId, status (success/error/waiting), mode, startedAt, stoppedAt. Filter by status and/or workflow_id. Requires your instance_url + n8n API key (_apiKey).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | REQUIRED — your n8n API key (Settings → n8n API → Create an API key). Sent as the X-N8N-API-KEY header. No shared key exists for this pack. |
| instance_url | string | yes | REQUIRED — your n8n instance base URL, e.g. "https://you.app.n8n.cloud" (n8n Cloud) or "https://n8n.example.com" (self-hosted). Must be a public https URL. |
| limit | number | – | Max executions (1-250, default 50). |
| status | string | – | Filter: "success" | "error" | "waiting". Omit for all. |
| workflow_id | string | – | Only executions of this workflow id. |
No output schema declared.
No examples provided.
n8n_list_workflows ~246
List workflows in YOUR n8n instance, with an active/inactive breakdown. Answers "how many active workflows do we have", "list our n8n workflows", "which workflows are turned on". Each workflow: id, name, active (on/off), createdAt, updatedAt, tags. Set active_only:true to list just the live ones. Requires your instance_url + n8n API key (_apiKey).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | REQUIRED — your n8n API key (Settings → n8n API → Create an API key). Sent as the X-N8N-API-KEY header. No shared key exists for this pack. |
| active_only | boolean | – | Only return active (turned-on) workflows. Default false (all). |
| instance_url | string | yes | REQUIRED — your n8n instance base URL, e.g. "https://you.app.n8n.cloud" (n8n Cloud) or "https://n8n.example.com" (self-hosted). Must be a public https URL. |
| limit | number | – | Max workflows to fetch (1-250, default 100). |
No output schema declared.
No examples provided.
How do I install the N8n MCP server?
N8n runs locally as an npm package, launched with npx -y @pipeworx/mcp-n8n. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-n8n
claude mcp add pipeworx-io-n8n -- npx -y @pipeworx/mcp-n8n
What is the N8n MCP server?
N8n is an MCP server listed in the public MCP registry as io.github.pipeworx-io/n8n. n8n MCP, query your own n8n instance (BYO). This page covers its npm package (@pipeworx/mcp-n8n).
Is the N8n MCP server safe to use?
N8n scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 N8n MCP server expose?
N8n exposes 3 tools: n8n_list_workflows, n8n_get_workflow, n8n_list_executions. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.
Is the N8n MCP server still maintained?
N8n is still listed as active in the MCP registry. We last reached this channel on 5 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 MCP server under?
N8n declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.