# @j0hanz/filesystem-mcp

Secure filesystem MCP server for reading, writing, searching, diffing, and patching files.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 2.0.0
- **Author:** j0hanz
- **License:** MIT
- **npm:** @j0hanz/filesystem-mcp
- **Source:** https://github.com/j0hanz/filesystem-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-01T14:50:57.077Z
- **Version scanned:** 2.0.0
- **CVEs:** none found by OSV at scan time

## Tools

18 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `create` — Create one or more files (max 100), writing or overwriting content and creating parent directories as needed.
- `delete` — Permanently delete one or more files, directories, or symlinks (max 1000 per call). This action is irreversible.
- `diff` — Compare two files and return a unified diff with line counts. Pass the two paths as a and b.
- `edit` — Apply sequential literal string replacements to one or more files (max 5 files per call).
- `list` — List sorted directory entries and an ASCII tree. maxDepth=1 is top-level.
- `move` — Move, rename, or copy files and directories to explicit destination paths (max 100 operations per call).
- `patch` — Apply a single-file unified diff to one file and write the result. Pass { path, diff }.
- `get-help`
- `read` — Read one or more text files and return content.
- `replace_text` — Bulk search-and-replace across files matching a glob pattern.
- `filesystem-mcp-instructions`
- `filesystem-mcp-file` — Read a file from the workspace. Subscribe to get updates when the file changes.
- `filesystem-mcp-result` — Ephemeral cached tool output. Listed via resources/list; entries expire after the cache TTL.
- `list_roots` — List the allowed workspace root directories. Call this first to discover what paths are accessible; all other tools are scoped to these roots. Allowed directori
- `search_text` — Search file contents by text or regex (grep-style). Returns matching lines with file path,
- `find_files` — Find files matching a glob pattern. Returns matched paths with optional metadata.
- `filesystem-mcp`
- `stat` — Get metadata for one or more files or directories: size, type, permissions, MIME type, timestamps, and tokenEstimate.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"filesystem\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@j0hanz/filesystem-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 39, ceiling 63 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40j0hanz%2Ffilesystem-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40j0hanz%2Ffilesystem-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40j0hanz%2Ffilesystem-mcp
- HTML page: https://forgeregistry.com/registry/%40j0hanz%2Ffilesystem-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.