N8n MCP
Debugging-first MCP server for n8n. Tools for workflow generation, linting, per-node execution diagnosis, and driving live n8n instances. Built for AI agents.
Is N8n MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare N8n MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: N8n MCP scores 33.0/100 (Grade D), ranked #1267 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.9/10; recent commits are unsigned; last pushed 2026-06-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How N8n MCP compares in MCP Servers
- #757 Banco MCP 33.3 +0.3
- #758 Fathom MCP Server 33.3 +0.3
- #759 N8n MCP 33.0 this agent
- #760 Nanobanana MCP Server 32.7 −0.3
- #761 Academia MCP 32.6 −0.4
Bars show each HVTrust score; the tick marks N8n MCP’s 33.0.
Where the 33.0 comes from
HVTrust dimensions vs the MCP Servers average
33.0 / 100 · 100.0% confidenceN8n MCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
16.6 / 100Supply Chain Trust
Common questions about N8n MCP
Does N8n MCP publish package provenance?
Does N8n MCP have an OpenSSF Scorecard?
Is N8n MCP actively maintained?
What license does N8n MCP use?
Are N8n MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to N8n MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain N8n MCP?
For maintainers
HVTrust scores N8n MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/automatelab-tech-n8n-mcp)
<a href="https://hvtracker.net/agents/automatelab-tech-n8n-mcp"><img src="https://hvtracker.net/badge/automatelab-tech-n8n-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON