@fkom13/mcp-sftp-orchestrator
npm
v11.3.0
Published by @fkom13 — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Un serveur MCP stdio pour l'orchestration de tâches distantes avec exécution hybride (synchrone/asynchrone) et configuration flexible.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Tool "task_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "cmd"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool task_exec
Tool "task_exec_interactive" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "cmd"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool task_exec_interactive
Tool "task_exec_sequence" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool task_exec_sequence
Tool "shell_create" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool shell_create
Tool "shell_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool shell_exec
Tool "shell_list" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool shell_list
Tool "shell_close" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool shell_close
Tool "tmux_create" appears to run shell commands or evaluate code (parameter "cmd"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool tmux_create
Tool "tmux_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "cmd"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool tmux_exec
In the server's implementation (`tunnels.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import fs from 'fs/promises'; import path from 'path'; import config from './con
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tunnels.js
Tool "task_exec" takes a command-shaped parameter "cmd" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool task_exec · inputSchema.properties.cmd
Tool "task_exec_interactive" takes a command-shaped parameter "cmd" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool task_exec_interactive · inputSchema.properties.cmd
Tool "task_exec_sequence" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool task_exec_sequence · inputSchema.properties.command
Tool "shell_exec" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool shell_exec · inputSchema.properties.command
Tool "tmux_create" takes a command-shaped parameter "start_cmd" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool tmux_create · inputSchema.properties.start_cmd
Tool "tmux_exec" takes a command-shaped parameter "cmd" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool tmux_exec · inputSchema.properties.cmd
Tool "task_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool task_exec
Tool "task_exec_interactive" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool task_exec_interactive
Tool "task_exec_sequence" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool task_exec_sequence
Tool "shell_create" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool shell_create
Tool "shell_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool shell_exec
Tool "shell_list" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool shell_list
Tool "shell_close" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool shell_close
Tool "tmux_create" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool tmux_create
Tool "tmux_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool tmux_exec
Each tool and what it can reach — statically extracted from the published source.
shell_closeruns code / shellshell_createruns code / shellshell_execruns code / shellshell_listruns code / shelltask_execruns code / shelltask_exec_interactiveruns code / shelltask_exec_sequenceruns code / shelltmux_createruns code / shelltmux_execruns code / shellapi_addno sensitive capabilityapi_checkno sensitive capabilityapi_listno sensitive capabilityapi_removeno sensitive capabilitycheck_api_healthno sensitive capabilitycompare_all_sourcesno sensitive capabilitydiff_filesno sensitive capabilitydiff_foldersno sensitive capabilityfile_editno sensitive capabilityfile_readno sensitive capabilityfile_writeno sensitive capabilityget_docker_logsno sensitive capabilityget_fail2ban_statusno sensitive capabilityget_pm2_logsno sensitive capabilityget_services_statusno sensitive capabilityget_system_resourcesno sensitive capabilityguideno sensitive capabilityhelpno sensitive capabilityinfra_overviewno sensitive capabilitypolicy_blocklist_addno sensitive capabilitypolicy_blocklist_listno sensitive capabilitypolicy_blocklist_removeno sensitive capabilitypool_statsno sensitive capabilityqueue_statsno sensitive capabilityserver_addno sensitive capabilityserver_listno sensitive capabilityserver_note_getno sensitive capabilityserver_note_listno sensitive capabilityserver_note_removeno sensitive capabilityserver_note_setno sensitive capabilityserver_removeno sensitive capabilitysnapshot_createno sensitive capabilitysnapshot_deleteno sensitive capabilitysnapshot_diffno sensitive capabilitysnapshot_listno sensitive capabilitysnapshot_restoreno sensitive capabilitysystem_diagnosticsno sensitive capabilitytail_fileno sensitive capabilitytask_historyno sensitive capabilitytask_logsno sensitive capabilitytask_queueno sensitive capabilitytask_retryno sensitive capabilitytask_statusno sensitive capabilitytask_transferno sensitive capabilitytask_transfer_multino sensitive capabilitytask_waitno sensitive capabilitytestno sensitive capabilitytest_toolno sensitive capabilitytest_tool_with_paramsno sensitive capabilitytmux_killno sensitive capabilitytmux_listno sensitive capabilitytmux_readno sensitive capabilitytunnel_allowlist_addno sensitive capabilitytunnel_allowlist_removeno sensitive capabilitytunnel_closeno sensitive capabilitytunnel_createno sensitive capabilitytunnel_listno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v11.3.0 latest |
A 92/100 | 25 | 1.13.0 | 2026-09-07 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @fkom13/mcp-sftp-orchestrator --online
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.