
Mcp Filesystem
io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026
Hardened filesystem for AI agents — jailed root, read-only default, traversal/symlink-safe.
Overview
A hardened local filesystem MCP server that gives an AI assistant jailed, read-only-by-default file access with traversal and symlink protections.
- What you can do
- Provides an AI assistant with filesystem access confined to a single jailed root directory, so it can read and work with files inside that root without reaching outside it. Access is read-only by default, and path handling is designed to resist directory traversal and symlink escapes. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Use it when you want an assistant to read or work with files in a specific local directory while keeping it contained to that directory and avoiding accidental writes by default.
- Requirements
- Runs as a local process on the user's machine via the npm package @infoinlet/mcp-filesystem over stdio. Desktop only; not executable in a web context. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Mcp Filesystem in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.

