registry / record
n8n-mcp
Does n8n-mcp MCP work in Claude Code and Cursor? Throne executed n8n-mcp mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: fit. Is n8n-mcp mcp safe? Static security scan: not run (the server did not launch far enough to scan). The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry n8n-mcp
sealed
- scan id
- 278651ca3781457db6b83c892a388bf5
- target
- n8n-mcp
- sealed at
- 2026-06-16 18:53:08Z
- evidence hash
- sha256:8dfd126ef7a91a4d2838e5fbf52ab32250e32b6704fd3a4083796da2314a9975
initialize ok: server n8n-documentation-mcp 2.57.4, negotiated protocolVersion 2025-03-26, capabilities ['resources', 'tools']
supported: tools/list (7 tools), resources/list (2); method not found (tolerated): prompts/list
all 7 tool inputSchemas are valid JSON Schema
called 7 of 7 tools (cap 10, strategy=serial): 3 ok, 4 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: tools_documentation:accepted (returned result); search_nodes:accepted (returned result); get_node:accepted (returned result); validate_node:accepted (returned result); get_template:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2025-03-26, server may have stale protocol handling
no streaming-capable tool declared by this server
read ui://n8n-mcp/operation-result (1 content blocks); subscribe capability not declared
ladder 1 overlapping tools_documentation calls: max_observed_stable_concurrency=1; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-03-26, first session was 2025-03-26)
initialize ok: server n8n-documentation-mcp 2.57.4, negotiated protocolVersion 2025-03-26, capabilities ['resources', 'tools'] [request_strategy=pipelined, connection_count=2, second connection established]
supported: tools/list (7 tools), resources/list (2); method not found (tolerated): prompts/list; notes: connection 2 confirms 7 tools
all 7 tool inputSchemas are valid JSON Schema
called 7 of 7 tools (cap 10, strategy=pipelined): 3 ok, 4 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: tools_documentation:accepted (returned result); search_nodes:accepted (returned result); get_node:accepted (returned result); validate_node:accepted (returned result); get_template:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2025-03-26, server may have stale protocol handling
no streaming-capable tool declared by this server
read ui://n8n-mcp/operation-result (1 content blocks); subscribe capability not declared
ladder 1/2/4/6 overlapping tools_documentation calls: max_observed_stable_concurrency=6; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-03-26, first session was 2025-03-26)
- target
- n8n-mcp npm
- engine
- sandboxed
- claude code
- calibration: partial recorded=9,spec=0,assumed=9
- cursor
- calibration: partial recorded=11,spec=0,assumed=7
- chatgpt desktop
- calibration: unavailable recorded=0,spec=2,assumed=16
- steps exercised
- 14 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 18:53:08Z
- evidence hash
- sha256:8dfd126ef7a91a4d2838e5fbf52ab32250e32b6704fd3a4083796da2314a9975
- valid until
- 2026-09-14
paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/n8n-mcp)maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.