io.github.Digital-Defiance/mcp-filesystem
NPM · @AI-CAPABILITIES-SUITE/MCP-FILESYSTEM
Advanced filesystem operations with strict security boundaries for AI agents
Available components
Last scanned (14 hours ago)
Scores higher than 38% of npm servers
Category Documents and Files
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 43 of 117 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency47
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 329 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 437 tokens (~36/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "fs_batch_operations" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 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.
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- CVE-2026-118764 affects this package: high ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 7 Nov 2026 · Analysed npm/@ai-capabilities-suite/mcp-filesystem@0.1.9
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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes | |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 117 packages
| Packages resolved | 117 |
|---|---|
| Deprecated | 1 |
| Stale | 42 |
| 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 →
fs_analyze_disk_usage ~38
Analyze disk usage
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | – |
| groupByType | string | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
fs_batch_operations ~30
Execute multiple filesystem operations atomically
| Name | Type | Req | Description |
|---|---|---|---|
| atomic | string | – | – |
| operations | string | yes | – |
No output schema declared.
No examples provided.
fs_build_index ~31
Build file index for fast searching
| Name | Type | Req | Description |
|---|---|---|---|
| includeContent | string | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
fs_compute_checksum ~28
Compute file checksums
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
fs_copy_directory ~42
Copy directories recursively
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| exclusions | string | – | – |
| preserveMetadata | string | – | – |
| source | string | yes | – |
No output schema declared.
No examples provided.
fs_create_symlink ~30
Create symbolic links
| Name | Type | Req | Description |
|---|---|---|---|
| linkPath | string | yes | – |
| targetPath | string | yes | – |
No output schema declared.
No examples provided.
fs_get_watch_events ~30
Get accumulated watch events
| Name | Type | Req | Description |
|---|---|---|---|
| clear | string | – | – |
| sessionId | string | yes | – |
No output schema declared.
No examples provided.
fs_search_files ~75
Search for files by name, content, or metadata
| Name | Type | Req | Description |
|---|---|---|---|
| fileTypes | string | – | – |
| maxSize | string | – | – |
| minSize | string | – | – |
| modifiedAfter | string | – | – |
| query | string | yes | – |
| searchType | string | – | – |
| useIndex | string | – | – |
No output schema declared.
No examples provided.
fs_stop_watch ~22
Stop watching a directory
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | – |
No output schema declared.
No examples provided.
fs_sync_directory ~40
Sync directories (copy only newer or missing files)
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| exclusions | string | – | – |
| source | string | yes | – |
No output schema declared.
No examples provided.
fs_verify_checksum ~35
Verify file checksums
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | – |
| checksum | string | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
fs_watch_directory ~36
Watch directory for filesystem changes
| Name | Type | Req | Description |
|---|---|---|---|
| filters | string | – | – |
| path | string | yes | – |
| recursive | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.Digital-Defiance/mcp-filesystem server?
io.github.Digital-Defiance/mcp-filesystem runs locally as an npm package, launched with npx -y @ai-capabilities-suite/mcp-filesystem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ai-capabilities-suite/mcp-filesystem
claude mcp add digital-defiance-mcp-filesystem -- npx -y @ai-capabilities-suite/mcp-filesystem
What is the io.github.Digital-Defiance/mcp-filesystem server?
io.github.Digital-Defiance/mcp-filesystem is listed in the public MCP registry as io.github.Digital-Defiance/mcp-filesystem. Advanced filesystem operations with strict security boundaries for AI agents. This page covers its npm package (@ai-capabilities-suite/mcp-filesystem).
Is the io.github.Digital-Defiance/mcp-filesystem server safe to use?
io.github.Digital-Defiance/mcp-filesystem scores 70 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 7 November 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 io.github.Digital-Defiance/mcp-filesystem server expose?
io.github.Digital-Defiance/mcp-filesystem exposes 12 tools: fs_batch_operations, fs_watch_directory, fs_get_watch_events, fs_stop_watch, fs_search_files, and 7 more. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.
Is the io.github.Digital-Defiance/mcp-filesystem server still maintained?
io.github.Digital-Defiance/mcp-filesystem is still listed as active in the MCP registry. We last reached this channel on 7 November 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 io.github.Digital-Defiance/mcp-filesystem server under?
io.github.Digital-Defiance/mcp-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.
What did VerifyMCP test on the io.github.Digital-Defiance/mcp-filesystem server?
VerifyMCP ran 16 checks on io.github.Digital-Defiance/mcp-filesystem, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.