Skills/PyPI/mcp-flowise

mcp-flowise@0.1.5

VERIFIED· startup only

Publisher claims: "MCP server exposing local Flowise chatflows as callable tools" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher pypi · publishing for 723 daysInstalls 31Last detonated 7d ago
$claude mcp add mcp-flowise -- uvx mcp-flowise
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified 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

Code inventory arrives with this version's next honeypot run.
It will ask for
unknown until the next run
Where it talks to
unknown until the next run
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Not enough was observed to say yet. Startup only; authenticated tool behavior not tested. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp-flowise` runs it now and prints the full answer.

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 (3 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-07 and scored it 82/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 3 scenarios · 0 deviations
t+CategoryObserved action
0.1sprocessexited 1: Supported clients: claude, cursor, free-code, vscode, windsurf
0.1sprocessexec /usr/bin/date
0.1sprocessexec /usr/bin/timeout
0.1sprocessexec /app/apps/web/node_modules/.bin/uvx
0.1sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/uvx
0.1sprocessexec /app/node_modules/.bin/uvx
0.1sprocessexec /pnpm/uvx
0.1sprocessexec /usr/local/sbin/uvx
0.1sprocessexec /usr/local/bin/uvx
0.1sprocessexec /usr/sbin/uvx
0.1sprocessexec /usr/bin/uvx
0.1sprocessexec /sbin/uvx
0.1sprocessexec /bin/uvx
0.1sclaimedno tools/list reply (exit 0)
0.1sprocessscript backend runs setup only
0.2sprocesssecond launch, clock +45 days, CI unset
0.3sprocessexec /usr/bin/faketime
0.3sprocessexited 1: Supported clients: claude, cursor, free-code, vscode, windsurf

Static findings

CRITICAL
Pipe-to-shell patternindex.js:31 · Pipe-to-shell pattern — downloads and immediately executes remote code" macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh\n" +Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST06
MEDIUM
npx invocation of non-well-known packageinstall.js:11 · npx invocation of non-well-known package — may execute untrusted code* npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client vscodeFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
Remote installer piped to shellindex.js:31 · Remote installer piped to shell" macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh\n" +Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST07
MEDIUM
npx invocation of non-well-known packageindex.js:5 · npx invocation of non-well-known package — may execute untrusted code* npx -y @smithery/cli install @pabloacastaneda86/mcp-flowise --client claudeFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageinstall.js:8 · npx invocation of non-well-known package — may execute untrusted code* npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client claudeFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageinstall.js:10 · npx invocation of non-well-known package — may execute untrusted code* npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client free-codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageinstall.js:12 · npx invocation of non-well-known package — may execute untrusted code* npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client windsurfFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageinstall.js:9 · npx invocation of non-well-known package — may execute untrusted code* npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client cursorFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈51 tok
1 file · 13 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for mcp-flowise@0.1.5 as of 7d ago. This is the package itself, not its dependencies.