{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-czlonkowski--n8n-mcp","slug":"czlonkowski--n8n-mcp","name":"n8n-mcp","type":"mcp","url":"https://www.n8n-mcp.com/","page_url":"https://unfragile.ai/czlonkowski--n8n-mcp","categories":["mcp-servers","app-builders","automation"],"tags":["mcp","mcp-server","n8n","workflows"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github-czlonkowski--n8n-mcp__cap_0","uri":"capability://search.retrieval.semantic.node.documentation.search.with.sqlite.full.text.indexing","name":"semantic node documentation search with sqlite full-text indexing","description":"Searches across 1,396 n8n nodes (812 core + 584 community) using a pre-built SQLite database with full-text search indexes, returning node metadata, parameter schemas, and usage examples without requiring external API calls. The system builds the index at compile-time by parsing n8n npm packages, then serves read-only queries at runtime via MCP protocol, enabling sub-100ms lookups for node discovery and documentation retrieval.","intents":["Find the right n8n node for a specific integration task without browsing the web","Retrieve parameter schemas and configuration requirements for a node before building a workflow","Discover alternative nodes that perform similar functions","Get code examples and credential setup instructions for a specific node"],"best_for":["AI assistants building n8n workflows in Claude Desktop or Cursor","Non-technical users who need node discovery without leaving their IDE","Workflow builders who want instant documentation without network latency"],"limitations":["Database is static and requires rebuild to reflect new n8n node releases","Search is limited to indexed fields (name, description, tags); custom metadata not in npm packages is unavailable","Full-text search performance degrades with very large result sets (1000+ matches)"],"requires":["SQLite 3.8+","Pre-built nodes.db file (included in distribution)","MCP client supporting stdio or HTTP transport"],"input_types":["text query (node name, keyword, category)","structured filter (node type, credential type)"],"output_types":["JSON node metadata (id, name, description, parameters, credentials)","structured parameter schema with validation rules","usage examples and documentation links"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_1","uri":"capability://search.retrieval.workflow.template.matching.and.retrieval.with.similarity.scoring","name":"workflow template matching and retrieval with similarity scoring","description":"Searches a database of 2,709 n8n templates using semantic similarity and keyword matching to find relevant workflow templates for a user's intent. The system ranks templates by relevance using a similarity service that compares user queries against template metadata (name, description, tags, use cases), returning ranked results with template structure, node composition, and deployment instructions.","intents":["Find a pre-built workflow template that matches a user's automation goal","Discover how other users have solved similar workflow problems","Get a starting point for a workflow instead of building from scratch","Understand common patterns for integrating specific services"],"best_for":["Non-technical users who want to reuse existing workflows","Workflow builders looking for patterns and best practices","Teams building similar automations across multiple instances"],"limitations":["Template relevance depends on quality of template metadata; poorly documented templates may not surface","Similarity scoring is keyword/metadata-based, not semantic understanding of workflow logic","Templates may reference deprecated nodes or outdated credential types"],"requires":["SQLite database with template metadata (included in distribution)","Similarity service implementation (src/services/similarity-service.ts)","MCP client connection"],"input_types":["natural language description of desired workflow","structured intent (integration names, trigger type, action type)"],"output_types":["ranked list of templates with relevance scores","template structure (nodes, connections, configuration)","template metadata (author, tags, use cases, prerequisites)"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_10","uri":"capability://memory.knowledge.template.management.system.with.metadata.extraction.and.pattern.analysis","name":"template management system with metadata extraction and pattern analysis","description":"Manages 2,709 workflow templates by extracting and indexing metadata (name, description, tags, use cases, node composition), enabling template discovery, pattern analysis, and reuse. The system analyzes template structure to identify common patterns, node combinations, and best practices, making this information available for workflow generation and learning.","intents":["Find templates that match a specific workflow pattern or use case","Learn common patterns for integrating specific services","Analyze template composition to understand best practices","Reuse template patterns in new workflows"],"best_for":["Workflow builders learning from existing templates","AI assistants generating workflows based on template patterns","Teams establishing workflow standards and best practices"],"limitations":["Template metadata quality varies; poorly documented templates may not be discoverable","Pattern analysis is based on node composition; cannot understand workflow logic","Templates may reference deprecated nodes or outdated patterns","Large number of templates (2,709) may make pattern analysis computationally expensive"],"requires":["Template metadata in SQLite database","Template structure definitions","Pattern analysis algorithms"],"input_types":["template search query","pattern criteria (nodes, integrations, use cases)"],"output_types":["template list with metadata","pattern analysis results (common node combinations, best practices)","template structure (nodes, connections, configuration)"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_11","uri":"capability://code.generation.editing.auto.fix.system.with.parameter.correction.and.credential.binding","name":"auto-fix system with parameter correction and credential binding","description":"Automatically corrects common workflow configuration errors by analyzing validation failures and generating corrected parameter values and credential bindings. The system uses heuristics and pattern matching to suggest fixes for missing credentials, invalid parameter types, and malformed expressions, enabling AI assistants to self-correct generated workflows.","intents":["Automatically fix common workflow configuration errors","Suggest correct parameter values based on node requirements","Recommend credential bindings for nodes that require authentication","Enable AI assistants to self-correct generated workflows"],"best_for":["AI assistants generating workflows that need auto-correction","Workflow builders who want quick fixes for validation errors","Automated workflow generation pipelines"],"limitations":["Auto-fix suggestions are heuristic-based and may not be correct for all use cases","Cannot fix errors that require domain knowledge (e.g., correct API endpoint for a service)","May suggest fixes that change workflow behavior unintentionally","Requires validation errors to be specific and actionable"],"requires":["Workflow JSON object with validation errors","Validation error details (node, parameter, error type)","Node definitions for parameter schema information","Optional: credential definitions for binding suggestions"],"input_types":["workflow JSON object","validation error list"],"output_types":["corrected workflow JSON","fix explanations (what changed and why)","confidence levels for each fix","alternative suggestions"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_12","uri":"capability://automation.workflow.multi.tenant.configuration.with.environment.based.deployment","name":"multi-tenant configuration with environment-based deployment","description":"Supports multi-tenant deployments through environment-based configuration, enabling different n8n instances, API credentials, and database backends to be configured per deployment. The system reads configuration from environment variables, supporting Docker, Railway, and HTTP server deployments with isolated tenant contexts.","intents":["Deploy n8n-mcp for multiple n8n instances with separate configurations","Configure different API credentials for different deployment environments","Support SaaS deployments where each tenant has their own n8n instance","Enable easy deployment across different platforms (Docker, Railway, HTTP)"],"best_for":["SaaS providers offering n8n-mcp as a service","Teams managing multiple n8n instances","Multi-tenant deployments requiring isolation"],"limitations":["Configuration is environment-based; no dynamic configuration changes without restart","Tenant isolation is logical (via configuration); no cryptographic isolation","Shared database backend may create performance bottlenecks for large numbers of tenants","Requires careful management of environment variables to prevent credential leakage"],"requires":["Environment variables for configuration (N8N_API_URL, N8N_API_KEY, etc.)","Docker or Node.js runtime for deployment","Optional: Railway account for Railway deployment"],"input_types":["environment variable configuration"],"output_types":["deployed n8n-mcp instance with tenant-specific configuration"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_13","uri":"capability://code.generation.editing.smart.parameter.suggestion.with.type.inference.and.validation","name":"smart parameter suggestion with type inference and validation","description":"Suggests appropriate parameter values for workflow nodes based on node type, parameter schema, and context from upstream nodes. The system infers parameter types from node definitions, validates suggested values against schema constraints, and provides intelligent suggestions that account for data flow through the workflow.","intents":["Get suggestions for parameter values when building a workflow","Understand what parameter types are expected for a node","Validate parameter values before deployment","Learn correct parameter usage from examples"],"best_for":["AI assistants generating workflow parameters","Workflow builders who want intelligent parameter suggestions","Teams enforcing parameter standards"],"limitations":["Suggestions are based on node schema; may not account for service-specific requirements","Type inference requires knowledge of upstream node outputs; may be incomplete in complex workflows","Cannot suggest values that require domain knowledge (e.g., correct API endpoint)","Validation is schema-based; may miss semantic errors"],"requires":["Node definition with parameter schema","Optional: upstream node outputs for context","Parameter validation rules"],"input_types":["node type","parameter name","optional: workflow context (upstream nodes, data flow)"],"output_types":["suggested parameter values","parameter type information","validation results","usage examples"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_14","uri":"capability://data.processing.analysis.telemetry.and.execution.analysis.with.performance.monitoring","name":"telemetry and execution analysis with performance monitoring","description":"Collects telemetry data on workflow execution, tool usage, and performance metrics, enabling analysis of workflow patterns, performance bottlenecks, and usage trends. The system tracks execution times, error rates, and tool call patterns, providing insights into workflow behavior and system performance.","intents":["Monitor workflow execution performance and identify bottlenecks","Analyze tool usage patterns to understand how n8n-mcp is being used","Track error rates and failure patterns","Optimize workflows based on execution data"],"best_for":["Teams optimizing workflow performance","Operators monitoring n8n-mcp system health","Analytics-driven workflow optimization"],"limitations":["Telemetry collection adds overhead to execution","Privacy concerns with collecting execution data; requires user consent","Analysis is retrospective; cannot predict future performance","Requires external storage for long-term telemetry retention"],"requires":["Telemetry collection infrastructure","Optional: external analytics service (e.g., Datadog, New Relic)","User consent for data collection"],"input_types":["execution events (start, end, error)","tool call events","performance metrics"],"output_types":["execution analysis reports","performance metrics (latency, throughput, error rate)","usage patterns and trends","optimization recommendations"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_2","uri":"capability://safety.moderation.multi.layer.workflow.validation.with.auto.fix.suggestions","name":"multi-layer workflow validation with auto-fix suggestions","description":"Validates n8n workflow configurations against multiple validation profiles (strict, lenient, custom) before deployment, checking for missing credentials, invalid parameter types, disconnected nodes, and expression syntax errors. The system uses specialized validators (src/services/workflow-validator.ts) that analyze workflow JSON structure and provide actionable auto-fix suggestions, including parameter corrections and credential binding recommendations, without requiring workflow execution.","intents":["Catch workflow configuration errors before deploying to n8n","Validate that all required credentials are properly configured","Check parameter types and expressions match node requirements","Get suggestions for fixing common workflow mistakes automatically"],"best_for":["AI assistants generating workflows that need validation before handoff","Workflow builders who want to validate changes before saving","Teams enforcing workflow quality standards across instances"],"limitations":["Validation is static and cannot detect runtime errors (e.g., API failures, data type mismatches at execution time)","Auto-fix suggestions are heuristic-based and may not be correct for all use cases","Custom validation rules require code changes; no dynamic rule configuration","Expression validation requires parsing n8n's custom expression language, which may have edge cases"],"requires":["Workflow JSON structure conforming to n8n schema","Validation profile definition (strict/lenient/custom)","Access to node definitions for parameter schema validation"],"input_types":["workflow JSON object","validation profile name (strict, lenient, custom)","optional: list of nodes to validate"],"output_types":["validation report with error/warning list","auto-fix suggestions with corrected parameters","severity levels (error, warning, info)","remediation steps for each issue"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_3","uri":"capability://safety.moderation.expression.language.validation.and.syntax.checking","name":"expression language validation and syntax checking","description":"Validates n8n's custom expression language (JavaScript-like syntax with special functions like $json, $env, $now) by parsing expressions against a grammar and checking for syntax errors, undefined variable references, and type mismatches. The system identifies invalid expressions in workflow parameters before deployment, providing line-by-line error reporting with suggestions for correction.","intents":["Validate that expressions in workflow parameters are syntactically correct","Check that referenced variables ($json, $env, etc.) are available in the expression context","Detect type mismatches in expression operations (e.g., string + number)","Get suggestions for fixing expression syntax errors"],"best_for":["AI assistants generating workflows with complex expressions","Workflow builders who want to validate expressions without executing","Teams enforcing expression quality standards"],"limitations":["Expression validation is syntax-based; cannot detect runtime errors (e.g., accessing undefined object properties)","Custom n8n expression functions may not be fully recognized by the validator","Context-dependent validation (e.g., $json structure) requires knowledge of upstream node outputs","Edge cases in n8n's expression language may not be handled correctly"],"requires":["Expression string in n8n syntax","Optional: context information (available variables, upstream node outputs)","Expression grammar definition"],"input_types":["expression string (e.g., '$json.data.name + \" - \" + $env.SUFFIX')","optional: context object with available variables"],"output_types":["validation result (valid/invalid)","error list with line/column numbers","suggestions for correction","type inference results"],"categories":["safety-moderation","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_4","uri":"capability://data.processing.analysis.workflow.diff.and.change.analysis.with.impact.assessment","name":"workflow diff and change analysis with impact assessment","description":"Analyzes differences between two workflow versions (original and modified) by comparing node configurations, connections, and parameters, then assesses the impact of changes on workflow behavior. The system identifies added/removed/modified nodes, changed parameter values, and altered connections, providing a structured diff report that helps users understand what changed and why.","intents":["Understand what changed between two versions of a workflow","Assess the impact of modifications on workflow behavior","Review changes before deploying an updated workflow","Track workflow evolution and audit changes over time"],"best_for":["Workflow builders reviewing AI-generated changes","Teams collaborating on workflow development","Audit and compliance scenarios requiring change tracking"],"limitations":["Diff analysis is structural; cannot predict actual runtime behavior changes","Impact assessment is heuristic-based and may miss subtle side effects","Large workflows with many nodes may produce verbose diffs","No support for workflow versioning or history tracking (requires external system)"],"requires":["Two workflow JSON objects (original and modified)","Node definitions for impact analysis","Optional: workflow execution history for context"],"input_types":["workflow JSON (original version)","workflow JSON (modified version)"],"output_types":["structured diff report (added/removed/modified nodes)","parameter change details (old value, new value, type)","connection change details (added/removed edges)","impact assessment (affected nodes, potential side effects)","human-readable change summary"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_5","uri":"capability://tool.use.integration.n8n.api.client.with.credential.management.and.workflow.crud.operations","name":"n8n api client with credential management and workflow crud operations","description":"Provides a typed API client (src/services/n8n-api-client.ts) that communicates with n8n instances via REST API, handling authentication, credential management, and workflow lifecycle operations (create, read, update, delete, execute). The client abstracts n8n API complexity, providing high-level methods for common operations while managing session state and error handling.","intents":["Create and deploy workflows to an n8n instance from an AI assistant","Update existing workflows with new configurations","Retrieve workflow execution history and logs","Manage credentials and authentication for workflow nodes","Execute workflows and retrieve results"],"best_for":["AI assistants that need to deploy generated workflows to n8n","Workflow builders automating workflow management tasks","Teams building custom n8n integrations"],"limitations":["Requires valid n8n API credentials (API key or OAuth token)","API rate limits apply; high-volume operations may be throttled","Workflow execution results are asynchronous; requires polling or webhook for completion status","Credential management is limited to n8n's built-in credential types; custom credential types may not be supported"],"requires":["n8n instance URL (self-hosted or cloud)","n8n API key or OAuth credentials","Network connectivity to n8n instance","TypeScript/Node.js runtime"],"input_types":["workflow JSON object","credential configuration (type, values)","workflow ID (for updates/deletes)","execution parameters"],"output_types":["workflow object (with ID, metadata)","execution result (status, output data, logs)","credential object (ID, type, metadata)","error responses with detailed messages"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_6","uri":"capability://safety.moderation.workflow.security.scanning.and.credential.exposure.detection","name":"workflow security scanning and credential exposure detection","description":"Scans workflow configurations for security vulnerabilities including hardcoded credentials, exposed secrets in expressions, insecure parameter values, and suspicious node combinations. The system analyzes workflow JSON and expressions using pattern matching and heuristics to identify potential security risks before deployment, providing remediation recommendations.","intents":["Detect hardcoded credentials or secrets in workflow configurations","Identify insecure parameter values (e.g., disabled SSL verification)","Find suspicious node combinations that might indicate malicious intent","Get recommendations for securing a workflow before deployment"],"best_for":["Security-conscious teams deploying AI-generated workflows","Compliance scenarios requiring security scanning","Teams with strict credential management policies"],"limitations":["Security scanning is pattern-based; may have false positives/negatives","Cannot detect all types of security vulnerabilities (e.g., logic flaws, authorization issues)","Requires knowledge of sensitive patterns (API keys, passwords, tokens) to detect","Custom credential types or obfuscated secrets may not be detected"],"requires":["Workflow JSON object","Pattern definitions for sensitive data (API keys, passwords, etc.)","Optional: credential type definitions for context"],"input_types":["workflow JSON object","optional: list of sensitive patterns to check for"],"output_types":["security scan report with vulnerabilities list","severity levels (critical, high, medium, low)","remediation recommendations","affected nodes and parameters"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_7","uri":"capability://tool.use.integration.dual.transport.mcp.server.with.stdio.and.http.support","name":"dual-transport mcp server with stdio and http support","description":"Implements the Model Context Protocol (MCP) server with support for both stdio transport (for local Claude Desktop integration) and HTTP transport (for remote/SaaS deployments). The server negotiates protocol versions, routes tool calls to appropriate handlers, and manages session state across different transport mechanisms, enabling the same tool set to work in multiple deployment scenarios.","intents":["Integrate n8n documentation and workflow tools into Claude Desktop","Deploy n8n-mcp as a remote service for cloud-based AI assistants","Support multiple concurrent AI assistant connections","Enable workflow building in different IDE environments (Cursor, Windsurf, VS Code)"],"best_for":["Claude Desktop users who want n8n integration in their IDE","Teams deploying n8n-mcp as a shared service","Multi-tenant SaaS deployments requiring HTTP transport"],"limitations":["Stdio transport is limited to local connections; no remote access","HTTP transport requires network security configuration (TLS, authentication)","Session management adds complexity for stateless deployments","Protocol version negotiation may fail with older MCP clients"],"requires":["MCP client supporting protocol version 2024-11-05 or compatible","For stdio: local Node.js runtime","For HTTP: Node.js runtime with network access, optional TLS certificates"],"input_types":["MCP protocol messages (tool calls, resource requests)","tool arguments (JSON)"],"output_types":["MCP protocol responses (tool results, resources)","structured JSON results"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_8","uri":"capability://tool.use.integration.two.tier.tool.system.with.documentation.and.management.tools","name":"two-tier tool system with documentation and management tools","description":"Separates tools into two tiers: documentation tools that work standalone with the local SQLite database (node search, template discovery, validation), and management tools that require external n8n API access (workflow CRUD, credential management, execution). This separation enables offline documentation access while maintaining clear boundaries for operations that require API credentials.","intents":["Access n8n documentation without requiring n8n API credentials","Perform workflow management operations that require API access","Understand which tools require external connectivity","Build workflows in offline scenarios using documentation tools"],"best_for":["Users who want documentation access without API setup","Deployments where API credentials are restricted","Offline-first scenarios where documentation is pre-indexed"],"limitations":["Documentation tools cannot perform mutations (create/update/delete)","Management tools require API credentials and network access","Clear separation means some workflows require both tool tiers","Documentation is static and requires rebuild for updates"],"requires":["For documentation tools: SQLite database (included)","For management tools: n8n API credentials and network access"],"input_types":["tool name and arguments"],"output_types":["tool results (documentation or mutation results)"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-czlonkowski--n8n-mcp__cap_9","uri":"capability://memory.knowledge.community.node.system.with.version.detection.and.compatibility.checking","name":"community node system with version detection and compatibility checking","description":"Manages 584 community nodes alongside 812 core nodes, with version detection and compatibility checking to ensure workflows use compatible node versions. The system tracks node versions, detects breaking changes between versions, and provides compatibility warnings when workflows reference nodes that may not be available in the target n8n instance.","intents":["Discover community nodes for specialized integrations","Check if a community node is compatible with the target n8n version","Get warnings about deprecated or incompatible nodes before deployment","Understand version requirements for workflows using community nodes"],"best_for":["Workflow builders using specialized community nodes","Teams managing multiple n8n instances with different versions","Deployments requiring compatibility verification"],"limitations":["Community node availability depends on n8n package registry; custom nodes not in registry are not tracked","Version compatibility checking requires knowledge of breaking changes; may miss subtle incompatibilities","Community nodes may be deprecated or unmaintained; no automatic detection of abandoned projects","Node version information must be kept up-to-date in the database"],"requires":["Community node metadata in SQLite database","Target n8n version information","Version compatibility definitions"],"input_types":["node name and version","target n8n version"],"output_types":["compatibility status (compatible, incompatible, deprecated)","version requirements","breaking change warnings","alternative node suggestions"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":53,"verified":false,"data_access_risk":"high","permissions":["SQLite 3.8+","Pre-built nodes.db file (included in distribution)","MCP client supporting stdio or HTTP transport","SQLite database with template metadata (included in distribution)","Similarity service implementation (src/services/similarity-service.ts)","MCP client connection","Template metadata in SQLite database","Template structure definitions","Pattern analysis algorithms","Workflow JSON object with validation errors"],"failure_modes":["Database is static and requires rebuild to reflect new n8n node releases","Search is limited to indexed fields (name, description, tags); custom metadata not in npm packages is unavailable","Full-text search performance degrades with very large result sets (1000+ matches)","Template relevance depends on quality of template metadata; poorly documented templates may not surface","Similarity scoring is keyword/metadata-based, not semantic understanding of workflow logic","Templates may reference deprecated nodes or outdated credential types","Template metadata quality varies; poorly documented templates may not be discoverable","Pattern analysis is based on node composition; cannot understand workflow logic","Templates may reference deprecated nodes or outdated patterns","Large number of templates (2,709) may make pattern analysis computationally expensive","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7453480137298893,"quality":0.35,"ecosystem":0.72,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:21.549Z","last_scraped_at":"2026-05-03T13:56:56.344Z","last_commit":"2026-05-02T20:04:07Z"},"community":{"stars":19284,"forks":3221,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=czlonkowski--n8n-mcp","compare_url":"https://unfragile.ai/compare?artifact=czlonkowski--n8n-mcp"}},"signature":"SQvN5M058cm14TB526ltjB7E+vuTX8cc+3myE0WO8/DLAOd5ALhwKn87h3Uv1xYqs8tPfrGlOuXBRYecO5ntCQ==","signedAt":"2026-06-23T01:54:09.166Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/czlonkowski--n8n-mcp","artifact":"https://unfragile.ai/czlonkowski--n8n-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=czlonkowski--n8n-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}