FileSystem MCP Server
PYPI · VS-FILESYSTEM-MCP-SERVER
Secure filesystem access for AI agents with configurable directory and file type restrictions
Available components
Last scanned (59 minutes ago)
Scores higher than 67% of PyPI 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 Security44
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (setup.py) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Oncorporation/filesystem_server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 870 tokens (~108/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (88% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 5 Nov 2026 · Analysed pypi/vs-filesystem-mcp-server@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Oncorporation/filesystem_server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Oncorporation/filesystem_server/.github/workflows/publish-mcp.yml@refs/heads/master |
| Rekor log index | 3242009452 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:54a50ad30fba31839de8b82a38557df8a260da900086c94f00760c8dc761f0d0 |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
| setup_py | unreviewed | <setup.py, unreviewed> |
Background: Why install scripts are a supply-chain risk →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 1 |
| 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 →
get_resource ~45
Get metadata and actions for a specific file or directory at the given path. Returns a resource object or an error if not found or not allowed.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
init ~147
Initialize and verify accessibility of allowed directories. Optionally list a directory and/or read a file if parameters are provided. Args: directory: Optional directory path to list contents file_path: Optional file path to read content Returns: A dictionary containing: - message: Status message ("OK" if all directories accessible, error description if not) - isError: Boolean indicating if there was an error - details: Additional information about directory accessibility - directory_contents: Optional list of directory contents if directory parameter provided - file_content: Optional file content if file_path parameter provided
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | – |
| file_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
list_directory ~194
List files and subdirectories in the given directory with optional progress reporting. Args: directory: The absolute or relative path to the directory (supports both / and \ separators). report_progress: Whether to include progress information in the response. batch_size: Number of items to process before reporting progress (default: 100). Returns: If report_progress is False: A list of file and directory names in the directory. If report_progress is True: A dictionary containing: - contents: List of file and directory names - progress_info: Dictionary with progress details - total_items: Total number of items found - processing_time: Time taken to process the directory If an error occurs, returns a dictionary with "error" and "error_message" keys.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_size | integer | – | – |
| directory | string | yes | – |
| report_progress | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
list_resources ~141
List all resources (files and directories) in the specified directory (or all allowed_dirs if not specified) in MCP resource format. Supports progress reporting for large workspaces. Args: directory: Directory to start from (optional, defaults to all allowed_dirs) report_progress: If True, returns progress info and batches batch_size: Number of resources per progress batch Returns: If report_progress is False: List of all resource objects If report_progress is True: Dict with contents, progress_info, total_items, processing_time
| Name | Type | Req | Description |
|---|---|---|---|
| batch_size | integer | – | – |
| directory | – | – | – |
| report_progress | boolean | – | – |
No output schema declared.
No examples provided.
read_file ~80
Read the content of a file. Args: file_path: The absolute or relative path to the file (supports both / and \ separators). Returns: The text content of the file. Raises: ValueError: If the file is not allowed, does not exist, or has a disallowed extension.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_file_binary ~49
Read the content of a file as base64-encoded bytes. Returns a dict with 'content_base64' (base64 string) or an error.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
write_file ~87
Write text content to a file. Args: file_path: The absolute or relative path to the file (supports both / and \ separators). content: The text content to write. Raises: ValueError: If the file is not allowed, parent directory issues, disallowed extension, or write fails.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| file_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | null | yes | – |
No examples provided.
write_file_binary ~127
Write binary content to a file from base64-encoded string. Returns a dict with success status or error. Args: file_path: The absolute or relative path to the file (supports both / and \ separators). content_base64: Base64-encoded binary content. Returns: {"success": true, "bytes_written": int, "encoding": "base64", "error": false} on success {"error": true, "error_message": str} on failure
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | – |
| file_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
How do I install the FileSystem MCP Server server?
FileSystem MCP Server runs locally as a PyPI package, launched with uvx vs-filesystem-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · vs-filesystem-mcp-server
claude mcp add oncorporation-filesystem-server -- uvx vs-filesystem-mcp-server
What is the FileSystem MCP Server server?
FileSystem MCP Server is listed in the public MCP registry as io.github.Oncorporation/filesystem-server. Secure filesystem access for AI agents with configurable directory and file type restrictions. This page covers its PyPI package (vs-filesystem-mcp-server).
Is the FileSystem MCP Server server safe to use?
FileSystem MCP Server scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 server expose?
FileSystem MCP Server exposes 8 tools: init, list_directory, read_file, list_resources, get_resource, and 3 more. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.
Is the FileSystem MCP Server server still maintained?
FileSystem MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 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 FileSystem MCP Server server under?
FileSystem MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.