File Organizer MCP Server
file-organizer-mcp
npm
v5.0.0
Published by kridaydave — 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.
Intelligent file organization MCP server for Claude with security-hardened operations, auto-categorization, and duplicate detection
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 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 |
| −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 10
high Reads a sensitive credential path or dumps the environment (dist/src/core/io/sensitive-files.js)MTC-SRC-006
In the server's implementation (`dist/src/core/io/sensitive-files.js:14`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ys /\.ssh\//i, /id_rsa/i, /id_ed25519/i, /id_ecdsa/i, /id_dsa/i, /\.pem$/i, /\.key$/i, /
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/src/core/io/sensitive-files.js
high Shell/command execution in server code (bin/file-organizer-mcp.mjs)MTC-SRC-002
In the server's implementation (`bin/file-organizer-mcp.mjs:16`): 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: port { execSync } from 'child_process'; import { fileURLToPath } from 'url'; const __filename = fileURLToPath(import.me
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 bin/file-organizer-mcp.mjs
high Shell/command execution in server code (bin/file-organizer-setup.mjs)MTC-SRC-002
In the server's implementation (`bin/file-organizer-setup.mjs:11`): 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: port { execSync } from 'child_process'; import { fileURLToPath } from 'url'; const __filename = fileURLToPath(import.me
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 bin/file-organizer-setup.mjs
high Shell/command execution in server code (dist/src/tui/setup-wizard.js)MTC-SRC-002
In the server's implementation (`dist/src/tui/setup-wizard.js:17`): 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: port { execSync } from "child_process"; import { updateUserConfig, getUserConfigPath, } from "../config.js"; import { de
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/src/tui/setup-wizard.js
medium Dynamic module load from a non-literal (bin/file-organizer-mcp.mjs)MTC-SRC-005
In the server's implementation (`bin/file-organizer-mcp.mjs:133`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ../dist/src/index.js'; import(serverRelativePath).catch(err => { error(`${RED}Failed to start server:${RESET}`, err.m
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 bin/file-organizer-mcp.mjs
medium Dynamic module load from a non-literal (bin/file-organizer-setup.mjs)MTC-SRC-005
In the server's implementation (`bin/file-organizer-setup.mjs:73`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ist/src/tui/index.js'; import(setupRelativePath).catch(err => { console.error(`${RED}Failed to start setup:${RESET}`,
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 bin/file-organizer-setup.mjs
low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (dist/scripts/security-gates/path-traversal-fuzz.js)MTC-SRC-006
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/security-gates/path-traversal-fuzz.js:288`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: }, { payload: "id_rsa.pub", description: "SSH public key" }, { payload: "id_rsa", description: "SSH pri
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/scripts/security-gates/path-traversal-fuzz.js
low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (dist/scripts/security-gates/sensitive-file-test.js)MTC-SRC-006
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/security-gates/sensitive-file-test.js:68`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: Files = [ ".ssh/id_rsa", ".ssh/id_ed25519", ".ssh/id_ecdsa", ".ssh/id_dsa", ".ss
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/scripts/security-gates/sensitive-file-test.js
low Shell/command execution in packaging/dev tooling (scripts/prepare.cjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/prepare.cjs:9`): 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 } = require('child_process'); const DIST_FILE = path.join(__dirname, '..', 'dist', 'src', 'index.js'); // C
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 scripts/prepare.cjs
low Package runs install-time scripts (postinstall)MTC-SUP-010
"file-organizer-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/postinstall.cjs
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package file-organizer-mcp
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions 2
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v5.0.0 latest |
A 92/100 | 10 | 1.13.0 | 2026-09-07 |
v3.4.2 |
A 92/100 | 12 | 1.13.0 | 2026-09-01 |
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.
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 file-organizer-mcp --onlineMore in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.