n8n@2.103.0
CAUTION· install onlyPublisher claims: "Bridges n8n's workflow automation platform with AI models, providing access to 543 n8n nodes, workflow templates, and AI-capable automation tools." Observed in sandbox: reads credential files.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 9 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
AUTH_TOKENAUTH_TOKEN_FILEN8N_MCP_ACCESS_TOKENConfiguration, not credentials: BASE_URL, CORS_ORIGIN, DISABLE_CONSOLE_OUTPUT, DISABLE_ENTERPRISE_TOOLS, DISABLED_TOOL_OPERATIONS, DISABLED_TOOLS, ENABLE_MULTI_TENANT, GIT_COMMIT, IS_CONTAINER, IS_DOCKER, MCP_MODE, MCP_REQUEST_ACTIVE, MCP_URL, N8N_MCP_DISABLE_UI_APPS, N8N_MCP_STDIO_MAX_BUFFER_SIZE, N8N_SKILLS_SOURCE, NODE_DB_PATH, PUBLIC_URL, TEST_ENVIRONMENT, TRUST_PROXY, USE_FIXED_HTTP- Where it talks to
- no vendor host named in the codeAlso your-server.com, n8n-mcp.com, n8n.cloud — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- read ~/.npmrc · no network
- What we could not test
- use of the skill by an agent
Connect it only under the guard, with no real credential files on the machine it runs on. It read ~/.npmrc, which is nothing an MCP server needs from a user. `--contain` makes those directories unreadable.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Refusal suppression; Access to sensitive file paths. Summary: reads credential files.
Behavior trace
Honeypot run · 16 s · 2 scenariosStatic findings
cp .env.example $PUBLISH_DIR/Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…ce has specific packages available in the Python runner environment, use them — don't refuse. When unsure, ask or write standard-library-only code. **❌ NOT available** (ra…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.# Check if .env existsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…oosing between Code node modes, or doing any custom data transformation in n8n. Always use this skill when a workflow needs a Code node — whether for data aggregation, filtering, AP…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- **SSH target** — `user@host` and how you authenticate (key path or the user confirms the agent already has access). Root or a sudo user.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…specific modules (e.g. `axios`, `lodash`, `crypto`), use them via `require()` — don't refuse. If unsure, ask or default to built-ins only. 7. **Wrong skill?** If you're wri…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.artifacts to share.** If you're working inside a git repo, confirm `.env` is git-ignoredFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.password, or `.env` from another n8n instance into this one. See `SECURITY.md` for theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.5. **`.env` and Caddy's `caddy_data` volume (the issued certs + ACME account key) are notFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.This skill takes a **fresh Linux VM** (Ubuntu/Debian, root or sudo SSH) to a **running,Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.cp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.instance) with `INSTANCE_AMBIGUOUS`. This is a safety net, not a substitute for rule 4: anFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.2. **Secrets live only in `.env`** (mode 600), referenced by the compose as `${VAR}`. NeverFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Pick `DATA_FOLDER` — an **absolute path**, e.g. `/opt/n8n`. The `DATA_FOLDER` value in `.env`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if [ ! -f .env ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…get_node detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are required for eac…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.echo "Creating .env file..."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Always access fields via `.json` (e.g. `item.json.name`, not `item.name`), and prefer the explicit `$input.first().json.field` over a bare `$json.field`.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.pkg.files = ['dist/**/*', 'ui-apps/dist/**/*', 'data/nodes.db', '.env.example', 'README.md', 'LICENSE'];Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return new URL(instanceUrl).origin + '/mcp-server/http';Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.- **Descriptive names** and `console.log()` for debugging (output goes to the browser console).Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Issue #711's `npx n8n-mcp` repro is handled by `stdio-wrapper.ts`, whichFix: Pin versions and sources; vendor anything fetched at install time."build:mcpb": "npm run build && npm run generate:mcpb-manifest && npx -y @anthropic-ai/mcpb validate manifest.json && npx -y @anthropic-ai/mcpb pack .",Fix: Pin versions and sources; vendor anything fetched at install time.// is for — the default suits the desktop and npx case the limit was raised for.Fix: Pin versions and sources; vendor anything fetched at install time.const result = await mcpServer.executeTool('get_node_essentials', { nodeType: 'nodes-base.httpRequest' });Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.// what happened, and on the npx path the user's machine has the version cached,Fix: Pin versions and sources; vendor anything fetched at install time.// the npx path — the one this diagnostic exists for — the logger producesFix: Pin versions and sources; vendor anything fetched at install time.if (disabledOperationsCache?.env === env) return disabledOperationsCache.value;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…blish`, `unpublish`, `revert`, `versions`, `delete`, `discover_assets`, `verify_mcp_server`, `update_integration`. Start with `action: "reference"`, then `discover_assets` → `create` → `mutate` (one resource at a time, always the latest ha…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.echo " - Users can run 'npx n8n-mcp' immediately after publish"Fix: Pin versions and sources; vendor anything fetched at install time.- **queue only:** `init-data.sh` → `<DATA_FOLDER>/init-data.sh`, then `chmod +x` itFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.if (disabledToolsCache?.env === cacheKey) return disabledToolsCache.value;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `chmod 600 .env`. Record the encryption key so the user can back it up off-box.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.- **Self-hosted (`npx n8n-mcp`, Docker)** — the server needs `N8N_API_URL` andFix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Reads credential files≈ +27 on the totalThe sandbox saw reads under ~/.ssh, ~/.aws, ~/.npmrc, ~/.config or similar. Read only files inside the project, and only the ones the task needs. Seen: ~/.npmrc.
- Unclaimed publisher≈ +8 on the totalClaim czlonkowski: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.