Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Digital-Defiance/mcp-filesystem

NPM · @AI-CAPABILITIES-SUITE/MCP-FILESYSTEM · SCANNED SEP 22

Advanced filesystem operations with strict security boundaries for AI agents

Available components

npm · @ai-capabilities-suite/mcp-filesystem 70
+3 this week 70 Trust /100
Trust breakdown (7 categories)

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
  • 44 of 120 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 283 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
Install

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

# add to Claude Code
claude mcp add digital-defiance-mcp-filesystem -- npx -y @ai-capabilities-suite/mcp-filesystem
// .cursor/mcp.json
{
  "mcpServers": {
    "digital-defiance-mcp-filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-capabilities-suite/mcp-filesystem"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "digital-defiance-mcp-filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-capabilities-suite/mcp-filesystem"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add digital-defiance-mcp-filesystem -- npx -y @ai-capabilities-suite/mcp-filesystem
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "digital-defiance-mcp-filesystem": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ai-capabilities-suite/mcp-filesystem"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add digital-defiance-mcp-filesystem --command npx --arg -y --arg @ai-capabilities-suite/mcp-filesystem
# ~/.hermes/config.yaml
mcp_servers:
  digital-defiance-mcp-filesystem:
    command: "npx"
    args: ["-y", "@ai-capabilities-suite/mcp-filesystem"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "digital-defiance-mcp-filesystem": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ai-capabilities-suite/mcp-filesystem"
      ]
    }
  }
}
# add to Vellum
assistant mcp add digital-defiance-mcp-filesystem -t stdio -c npx -a -y @ai-capabilities-suite/mcp-filesystem
// mcp.json
{
  "mcpServers": {
    "digital-defiance-mcp-filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-capabilities-suite/mcp-filesystem"
      ]
    }
  }
}
Changelog

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.

  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 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.

  • 20 Sept 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 19 Sept 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 18 Sept 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.

  • 16 Sept 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 15 Sept 26 −3
    • Security disclosure: pass → unverified ▼ functional
    • Stability: pass → 0.77 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 22 Sept 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 1 finding
ID CVE Severity Vector Fix available
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 120 packages
Packages resolved 120
Deprecated 1
Stale 43
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~437 tokens

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 →

Tool Tokens
fs_analyze_disk_usage ~38

Analyze disk usage

NameTypeReqDescription
depthstring––
groupByTypestring––
pathstringyes–

No output schema declared.

No examples provided.

fs_batch_operations ~30

Execute multiple filesystem operations atomically

NameTypeReqDescription
atomicstring––
operationsstringyes–

No output schema declared.

No examples provided.

fs_build_index ~31

Build file index for fast searching

NameTypeReqDescription
includeContentstring––
pathstringyes–

No output schema declared.

No examples provided.

fs_compute_checksum ~28

Compute file checksums

NameTypeReqDescription
algorithmstring––
pathstringyes–

No output schema declared.

No examples provided.

fs_copy_directory ~42

Copy directories recursively

NameTypeReqDescription
destinationstringyes–
exclusionsstring––
preserveMetadatastring––
sourcestringyes–

No output schema declared.

No examples provided.

fs_create_symlink ~30

Create symbolic links

NameTypeReqDescription
linkPathstringyes–
targetPathstringyes–

No output schema declared.

No examples provided.

fs_get_watch_events ~30

Get accumulated watch events

NameTypeReqDescription
clearstring––
sessionIdstringyes–

No output schema declared.

No examples provided.

fs_search_files ~75

Search for files by name, content, or metadata

NameTypeReqDescription
fileTypesstring––
maxSizestring––
minSizestring––
modifiedAfterstring––
querystringyes–
searchTypestring––
useIndexstring––

No output schema declared.

No examples provided.

fs_stop_watch ~22

Stop watching a directory

NameTypeReqDescription
sessionIdstringyes–

No output schema declared.

No examples provided.

fs_sync_directory ~40

Sync directories (copy only newer or missing files)

NameTypeReqDescription
destinationstringyes–
exclusionsstring––
sourcestringyes–

No output schema declared.

No examples provided.

fs_verify_checksum ~35

Verify file checksums

NameTypeReqDescription
algorithmstring––
checksumstringyes–
pathstringyes–

No output schema declared.

No examples provided.

fs_watch_directory ~36

Watch directory for filesystem changes

NameTypeReqDescription
filtersstring––
pathstringyes–
recursivestring––

No output schema declared.

No examples provided.

Common questions

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 1 known advisory against it as of 22 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 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 22 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 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.