Bach Filecommander MCP Server

bach-filecommander-mcp npm v1.7.4

Published by lukisch — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A comprehensive MCP server providing 43 tools for filesystem operations, process management, interactive sessions, async file search, JSON repair, encoding fix, duplicate detection, OCR, ZIP archives, and Markdown export

Trust grade
B
87/100
Last scanned get badge →
Trust
B · 87/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 94 − adoption risk = 87/100

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 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

2. Client adoption risk — 94 − 7 = 87. 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:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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.

Findings 19

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([fc_read_file]) and tools that can send data out ([fc_execute_command, fc_start_session]) are exposed together. An agent can move private data to the sink.

Evidence: sources [fc_read_file] → sinks [fc_execute_command, fc_start_session]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow fc_read_file → fc_execute_command

high Tool "fc_execute_command" exposes command/code executionMTC-CAP-001

Tool "fc_execute_command" appears to run shell commands or evaluate code (keyword "execute command" 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 fc_execute_command

high Tool "fc_start_session" exposes command/code executionMTC-CAP-001

Tool "fc_start_session" appears to run shell commands or evaluate code (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 fc_start_session

high Shell/command execution in server code (dist/index.js)MTC-SRC-002

In the server's implementation (`dist/index.js:25`): 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: execSync, spawn } from "child_process"; import { promisify } from "util"; import * as yaml from 'js-yaml'; import * as t

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 dist/index.js

medium Untrusted input concatenated into a command sink (dist/index.js)MTC-SRC-009

In the server's implementation (`dist/index.js:3520`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: /g, '/')}`; execSync(`"${browser}" --headless --disable-gpu --print-to-pdf="${outputPath}" --no-pdf-header-f

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 dist/index.js

medium Tool "fc_write_file" can modify the filesystemMTC-CAP-002

Tool "fc_write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool fc_write_file

medium Tool "fc_delete_file" can modify the filesystemMTC-CAP-002

Tool "fc_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool fc_delete_file

medium Tool "fc_edit_file" can modify the filesystemMTC-CAP-002

Tool "fc_edit_file" can write, overwrite or delete files (keyword "edit_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool fc_edit_file

medium Unconstrained command parameter "command" on "fc_execute_command"MTC-CAP-006

Tool "fc_execute_command" 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 fc_execute_command · inputSchema.properties.command

medium Unconstrained command parameter "command" on "fc_start_session"MTC-CAP-006

Tool "fc_start_session" 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 fc_start_session · inputSchema.properties.command

low Mutating tool "fc_write_file" declares no destructiveHintMTC-CAP-005

Tool "fc_write_file" 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 fc_write_file

low Mutating tool "fc_delete_file" declares no destructiveHintMTC-CAP-005

Tool "fc_delete_file" 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 fc_delete_file

low Mutating tool "fc_execute_command" declares no destructiveHintMTC-CAP-005

Tool "fc_execute_command" 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 fc_execute_command

low Mutating tool "fc_edit_file" declares no destructiveHintMTC-CAP-005

Tool "fc_edit_file" 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 fc_edit_file

low Mutating tool "fc_start_session" declares no destructiveHintMTC-CAP-005

Tool "fc_start_session" 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 fc_start_session

low Unconstrained path parameter "path" on "fc_read_file"MTC-CAP-008

Tool "fc_read_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool fc_read_file · inputSchema.properties.path

low Unconstrained path parameter "path" on "fc_write_file"MTC-CAP-008

Tool "fc_write_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool fc_write_file · inputSchema.properties.path

low Unconstrained path parameter "path" on "fc_delete_file"MTC-CAP-008

Tool "fc_delete_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool fc_delete_file · inputSchema.properties.path

low Unconstrained path parameter "path" on "fc_edit_file"MTC-CAP-008

Tool "fc_edit_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool fc_edit_file · inputSchema.properties.path

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • fc_delete_filewrites files
  • fc_edit_filewrites files
  • fc_execute_commandruns code / shell
  • fc_read_filereads sensitive data
  • fc_start_sessionruns code / shell
  • fc_write_filewrites files
  • fc_archiveno sensitive capability
  • fc_batch_renameno sensitive capability
  • fc_checksumno sensitive capability
  • fc_cleanup_fileno sensitive capability
Show 34 more tools ↓
  • fc_clear_searchno sensitive capability
  • fc_close_sessionno sensitive capability
  • fc_convert_formatno sensitive capability
  • fc_copyno sensitive capability
  • fc_create_directoryno sensitive capability
  • fc_delete_directoryno sensitive capability
  • fc_detect_duplicatesno sensitive capability
  • fc_file_infono sensitive capability
  • fc_fix_encodingno sensitive capability
  • fc_fix_jsonno sensitive capability
  • fc_folder_diffno sensitive capability
  • fc_get_search_resultsno sensitive capability
  • fc_get_timeno sensitive capability
  • fc_kill_processno sensitive capability
  • fc_list_directoryno sensitive capability
  • fc_list_processesno sensitive capability
  • fc_list_searchesno sensitive capability
  • fc_list_sessionsno sensitive capability
  • fc_md_to_htmlno sensitive capability
  • fc_md_to_pdfno sensitive capability
  • fc_moveno sensitive capability
  • fc_ocrno sensitive capability
  • fc_read_multiple_filesno sensitive capability
  • fc_read_outputno sensitive capability
  • fc_safe_deleteno sensitive capability
  • fc_search_filesno sensitive capability
  • fc_send_inputno sensitive capability
  • fc_set_languageno sensitive capability
  • fc_set_safe_modeno sensitive capability
  • fc_start_processno sensitive capability
  • fc_start_searchno sensitive capability
  • fc_stop_searchno sensitive capability
  • fc_str_replaceno sensitive capability
  • fc_validate_jsonno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan 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.

VersionScoreFindingsEngineScanned
v1.7.4 latest B 87/100 19 1.13.0 2026-09-07

Embed this score

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.

MCP Trust Score: B · 87/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bach-filecommander-mcp/badge.svg)](https://mcptrustchecker.com/registry/bach-filecommander-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/bach-filecommander-mcp"><img src="https://mcptrustchecker.com/registry/bach-filecommander-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bach-filecommander-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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 bach-filecommander-mcp --online

Use the free API → How scoring works

More in Web, Search & Scraping