Skills/npm/langflow-mcp-server

langflow-mcp-server@4.13.0

CAUTION

Publisher claims: "Integration for Langflow API 1.13.0 via Model Context Protocol (MCP)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher nobrainer-tech · joined 7 days agoInstalls 3,941Last detonated 5d ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-10-29 and scored it 78/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. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.9sprocessdependency install exit 1
0.9sprocessexec /usr/bin/timeout
0.9sprocessexited 1: Node.js v22.23.4
0.9sclaimedno tools/list reply (exit 1)
0.9sprocessscript backend runs setup only

Static findings

HIGH
Access to sensitive file pathspackage.json:62 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Process kill commanddist/mcp/tools-consolidated.js:1274 · Process kill command — agent can terminate processesFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commanddist/mcp/tools.js:4007 · Process kill command — agent can terminate processesFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Stripe-like API key pattern detecteddist/__tests__/fixtures/api-keys.js:17 · Stripe-like API key pattern detected — possible hardcoded or harvested keyFix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03

What would make this Verified

2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim nobrainer-tech: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
  3. 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.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  5. Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  6. Stripe-like API key pattern detected≈ +2 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim nobrainer-tech