Filesystem
NPM · FILESYSTEM-MCP · SCANNED SEP 20
Read, create, and edit files.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 196 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 419 tokens (~104/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Filesystem MCP server?
Filesystem runs locally as an npm package, launched with npx -y filesystem-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · filesystem-mcp
claude mcp add domdomegg-filesystem-mcp -- npx -y filesystem-mcp
{
"mcpServers": {
"domdomegg-filesystem-mcp": {
"command": "npx",
"args": [
"-y",
"filesystem-mcp"
]
}
}
} {
"servers": {
"domdomegg-filesystem-mcp": {
"command": "npx",
"args": [
"-y",
"filesystem-mcp"
]
}
}
} codex mcp add domdomegg-filesystem-mcp -- npx -y filesystem-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"domdomegg-filesystem-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"filesystem-mcp"
],
"enabled": true
}
}
} openclaw mcp add domdomegg-filesystem-mcp --command npx --arg -y --arg filesystem-mcp
mcp_servers:
domdomegg-filesystem-mcp:
command: "npx"
args: ["-y", "filesystem-mcp"] {
"McpServers": {
"domdomegg-filesystem-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"filesystem-mcp"
]
}
}
} assistant mcp add domdomegg-filesystem-mcp -t stdio -c npx -a -y filesystem-mcp
{
"mcpServers": {
"domdomegg-filesystem-mcp": {
"command": "npx",
"args": [
"-y",
"filesystem-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/filesystem-mcp@1.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create Create ~66
Create or overwrite a file with the specified content. - Creates parent directories if they don't exist - Overwrites existing files without warning - Use absolute paths
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content to write to the file |
| path | string | yes | Absolute path where file will be created |
No output schema declared.
No examples provided.
insert Insert ~116
Insert text at a specific line in a file. - insert_line = 0: Insert at the beginning - insert_line = N: Insert after line N - insert_line = -1: Insert at the end - insert_text should typically end with a newline - Use absolute paths
| Name | Type | Req | Description |
|---|---|---|---|
| insert_line | integer | yes | Line number to insert after (0 = beginning, -1 = end) |
| insert_text | string | yes | Text to insert (should end with newline) |
| path | string | yes | Absolute path to file |
No output schema declared.
No examples provided.
str_replace String Replace ~104
Replace an exact string in a file. - old_str must match exactly and be unique in the file - If old_str appears 0 times or more than once, the operation fails - If new_str is omitted, old_str is deleted - Use absolute paths
| Name | Type | Req | Description |
|---|---|---|---|
| new_str | string | – | Replacement string (omit to delete) |
| old_str | string | yes | Exact string to find (must be unique) |
| path | string | yes | Absolute path to file |
No output schema declared.
No examples provided.
view View ~133
View file contents or list directory. For files: - Returns content with line numbers (format: " N\t<content>") - Use view_range to read specific lines [start, end] (1-indexed, inclusive) - Large files are truncated at 16000 characters For directories: - Lists contents with type indicator (/ for directories) - Shows 2 levels deep by default - Ignores hidden files and node_modules
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to file or directory |
| view_range | array | – | Line range [start, end] for text files (1-indexed, inclusive) |
No output schema declared.
No examples provided.
What is the Filesystem MCP server?
Filesystem is an MCP server listed in the public MCP registry as io.github.domdomegg/filesystem-mcp. Read, create, and edit files. This page covers its npm package (filesystem-mcp).
Is the Filesystem MCP server safe to use?
Filesystem scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Filesystem MCP server expose?
Filesystem exposes 4 tools: view, create, str_replace, insert. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.
Is the Filesystem MCP server still maintained?
Filesystem is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Filesystem MCP server under?
Filesystem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.