Filesystem (your-username) MCP Server

filesystem-mcp-server npm v2.0.0

Published by your-username — 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, secure, cross-platform MCP server for advanced file system operations

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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
A Why this grade threat 100 − adoption risk = 96/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 − 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 − 4 = 96. 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
−3 capability blast radius (moderate) — 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 9

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

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

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

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

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

Tool "move_file" can write, overwrite or delete files (keyword "move_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 move_file

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

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

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

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

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

Tool "move_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 move_file

low Unconstrained path parameter "filePath" on "read_file"MTC-CAP-008

Tool "read_file" takes a path parameter "filePath" 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 read_file · inputSchema.properties.filePath

low Unconstrained path parameter "filePath" on "write_file"MTC-CAP-008

Tool "write_file" takes a path parameter "filePath" 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 write_file · inputSchema.properties.filePath

low Unconstrained path parameter "filePath" on "delete_file"MTC-CAP-008

Tool "delete_file" takes a path parameter "filePath" 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 delete_file · inputSchema.properties.filePath

Tools 24

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

  • delete_filewrites files
  • move_filewrites files
  • read_filereads sensitive data
  • write_filewrites files
  • batch_copyno sensitive capability
  • batch_deleteno sensitive capability
  • change_ownershipno sensitive capability
  • change_permissionsno sensitive capability
  • compressno sensitive capability
  • copy_fileno sensitive capability
Show 14 more tools ↓
  • create_directoryno sensitive capability
  • create_symlinkno sensitive capability
  • delete_directoryno sensitive capability
  • extractno sensitive capability
  • file_existsno sensitive capability
  • get_file_infono sensitive capability
  • list_archiveno sensitive capability
  • list_directoryno sensitive capability
  • list_watchersno sensitive capability
  • read_symlinkno sensitive capability
  • search_filesno sensitive capability
  • start_watchingno sensitive capability
  • stop_watchingno sensitive capability
  • update_timestampsno sensitive capability

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
v2.0.0 latest A 96/100 9 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: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/filesystem-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/filesystem-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/filesystem-mcp-server"><img src="https://mcptrustchecker.com/registry/filesystem-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/filesystem-mcp-server/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 filesystem-mcp-server --online

Use the free API → How scoring works

Other implementations of Filesystem 22

Independent packages implementing the same tool, scanned with the same engine. Compare all 23 side by side →

More in Web, Search & Scraping