A
licenseNot graded
qualityD
maintenanceStatically analyzes exported n8n automation workflows for security issues and returns structured findings.
MIT
n8n-lint
by shulkyn-dev
Related Servers
Alternatives to n8n-lint
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to lint and format n8n workflow JSON over MCP, reporting issues with line-level detail and applying safe fixes.1MIT
- AlicenseAqualityBmaintenanceEnables conversational analysis of n8n workflows and Make scenarios for silent-failure risks, with tools to explain findings, compare workflow versions, and list rules.410 npmMIT
- AlicenseBqualityCmaintenanceSafe MCP server and CLI tool for testing, scoring, and inspecting n8n workflows. Features 19 tools for workflow testing, execution traces, tiered scoring, and a built-in node catalog with 800+ node types. Designed with safety-first approach: no credential management, no secrets lifecycle, no auto-fix loops.191MIT
- AlicenseAqualityAmaintenanceProvides ops-focused n8n tools for MCP-compatible agents, enabling listing, inspecting, triggering, validating, managing tags, running security audits, and safely editing n8n workflows with auto-backup and confirm gates.2016 npm1MIT
- FlicenseNot gradedqualityCmaintenanceConverts natural language descriptions into validated, production-ready n8n workflows with automatic error fixing and architecture recommendations.16 npm22-
TDQS
A3.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct role: lint_workflow performs the analysis, list_rules enumerates rule metadata, and explain_rule provides rationale and fix guidance for a specific rule. There is no meaningful overlap, and an agent can easily select the right tool from the descriptions alone.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case: lint_workflow, list_rules, explain_rule. This predictability makes the toolset easy to scan and remember.
Tool Count5/5
Three tools is exactly right for this focused linter server: one action tool and two rule-inspection tools. Each tool earns its place without redundancy or unnecessary surface area.
Completeness4/5
The core workflow of linting a workflow, listing rules, and explaining rules is fully covered. Minor gaps exist around rule configuration (e.g., enabling/disabling rules) or automated fixes, which are common in linters but not strictly necessary for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues