THRONE
See report Verify server

registry / record

n8n-mcp

npm / sealed 2026-06-13 / No. 6ab46f3d

> throne registry n8n-mcp sealed
receiptsealed evidence
scan id
6ab46f3da6ab47c2a85d3b60472b8a58
target
n8n-mcp
sealed at
2026-06-13 08:59:15Z
evidence hash
sha256:99e5b515fdb653bcbedcd5c6b93ef6a7ac501dbda5529cc934e6abc148593261
01connectPASS6.9s

initialize ok: server n8n-documentation-mcp 2.57.3, negotiated protocolVersion 2025-03-26, capabilities ['resources', 'tools']

02discoverPASS7ms

supported: tools/list (7 tools), resources/list (2); method not found (tolerated): prompts/list

03validate_schemasPASS26ms

all 7 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS65ms

called 7 of 7 tools (cap 10): 3 ok, 4 returned tool-level errors (expected for synthesized args)

05error_handlingPASS5.2s

structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS0ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS28ms

read ui://n8n-mcp/operation-result (1 content blocks); subscribe capability not declared (pass-na)

08concurrent_callsPASS16ms

ladder 1/2/4/8 overlapping tools_documentation calls: max_observed_stable_concurrency=8; all ids answered exactly once at every level

09reconnectPASS2.1s

transport closed and relaunched; re-handshake ok (protocolVersion 2025-03-26, first session was 2025-03-26)

01connectPASS1.1s

initialize ok: server n8n-documentation-mcp 2.57.3, negotiated protocolVersion 2025-03-26, capabilities ['resources', 'tools']

02discoverPASS7ms

supported: tools/list (7 tools), resources/list (2); method not found (tolerated): prompts/list

03validate_schemasPASS27ms

all 7 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS68ms

called 7 of 7 tools (cap 10): 3 ok, 4 returned tool-level errors (expected for synthesized args)

05error_handlingPASS4.2s

structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS0ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS34ms

read ui://n8n-mcp/operation-result (1 content blocks); subscribe capability not declared (pass-na)

08concurrent_callsPASS16ms

ladder 1/2/4/8 overlapping tools_documentation calls: max_observed_stable_concurrency=8; all ids answered exactly once at every level

09reconnectPASS1.1s

transport closed and relaunched; re-handshake ok (protocolVersion 2025-03-26, first session was 2025-03-26)

chatgpt desktopemulation profile pending real-traffic captureCOMING SOON
SECURITY: NOT RUN
VERDICT: FIT TO SHIPSANDBOXED RUN — submitted server executed in a disposable microVM — compatibility: 0 fail / 0 warn across 2 clients / security scan skippedsealed by THRONE / No. 6ab46f3d / 2026-06-13
THRONE: FIT TO SHIPwear the crown

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.

[![THRONE: FIT TO SHIP](https://api.usethrone.dev/api/badge/n8n-mcp)](https://usethrone.dev/server/n8n-mcp)
executed in a disposable microVM, created for this scan and destroyed after it. nothing outlives a run.

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.