Verfy

MCP servers / n8n-mcp

MCP tool changes

n8n-mcp

No tool definition changed across the 6 releases that started, up to 2.102.0.

npm package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. npm page · Method and limits · this data as JSON.

Release by release

2.101.4 → 2.102.0

minor release, 9 November 2026

No tool definition changed.

2.101.3 → 2.101.4

patch release, 7 November 2026

No tool definition changed.

2.101.2 → 2.101.3

patch release, 7 November 2026

No tool definition changed.

2.101.1 → 2.101.2

patch release, 7 November 2026

No tool definition changed.

2.101.0 → 2.101.1

patch release, 6 November 2026

No tool definition changed.

Releases tried: 2.101.0 (2026-11-03); 2.101.1 (2026-11-06); 2.101.2 (2026-11-07); 2.101.3 (2026-11-07); 2.101.4 (2026-11-07); 2.102.0 (2026-11-09).

Tools in 2.102.0

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.

Tools in 2.102.0
ToolDescriptionPin
tools_documentationGet documentation for n8n MCP tools. Call without parameters for quick start guide. Use topic parameter to get documentation for specific tools. Use depth='full' for comprehensive documentation.2e92bfc26f96
search_nodesSearch n8n nodes by keyword with optional real-world examples. Pass query as string. Example: query="webhook" or query="database". Returns max 20 results. Use includeExamples=true to get top 2 template configs per node.f44ea626221f
get_nodeGet node info with progressive detail levels and multiple modes. Detail: minimal (~200 tokens), standard (~1-2K, default), full (~3-8K). Modes: info (default), docs (markdown documentation), search_properties (find properties), versions/compare/breaking/migrations (version info). Use format='docs' for readable documentation, mode='search_properties' with propertyQuery for finding specific fields.5874c16076bb
validate_nodeValidate n8n node configuration. Use mode='full' for comprehensive validation with errors/warnings/suggestions, mode='minimal' for quick required fields check. Example: nodeType="nodes-base.slack", config={resource:"channel",operation:"create"}2b1346e8d56e
get_templateGet template by ID. Use mode to control response size: nodes_only (minimal), structure (nodes+connections), full (complete workflow).cb5268437f51
search_templatesSearch templates with multiple modes. Use searchMode='keyword' for text search, 'by_nodes' to find templates using specific nodes, 'by_task' for curated task-based templates, 'by_metadata' for filtering by complexity/setup time/services, 'patterns' for lightweight workflow pattern summaries mined from 2700+ templates.ad3c722e2878
validate_workflowFull workflow validation: structure, connections, expressions, AI tools. Returns errors/warnings/fixes. Essential before deploy.074021c93e9d

Lock these tools

Pin what n8n-mcp serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout
- uses: verfy-dev/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.