io.github.j0hanz/filesystem-context
NPM · @J0HANZ/FILESYSTEM-CONTEXT-MCP · SCANNED AUG 6
🔍 Read-only MCP server for secure filesystem exploration, searching, and analysis
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read.Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read.Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Tool Safety–
Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
Capabilities0
- Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the io.github.j0hanz/filesystem-context MCP server?
io.github.j0hanz/filesystem-context runs locally as an npm package, launched with npx -y @j0hanz/filesystem-context-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 · @j0hanz/filesystem-context-mcp
claude mcp add j0hanz-filesystem-context -- npx -y @j0hanz/filesystem-context-mcp
{
"mcpServers": {
"j0hanz-filesystem-context": {
"command": "npx",
"args": [
"-y",
"@j0hanz/filesystem-context-mcp"
]
}
}
} {
"servers": {
"j0hanz-filesystem-context": {
"command": "npx",
"args": [
"-y",
"@j0hanz/filesystem-context-mcp"
]
}
}
} codex mcp add j0hanz-filesystem-context -- npx -y @j0hanz/filesystem-context-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"j0hanz-filesystem-context": {
"type": "local",
"command": [
"npx",
"-y",
"@j0hanz/filesystem-context-mcp"
],
"enabled": true
}
}
} openclaw mcp add j0hanz-filesystem-context --command npx --arg -y --arg @j0hanz/filesystem-context-mcp
mcp_servers:
j0hanz-filesystem-context:
command: "npx"
args: ["-y", "@j0hanz/filesystem-context-mcp"] {
"McpServers": {
"j0hanz-filesystem-context": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@j0hanz/filesystem-context-mcp"
]
}
}
} assistant mcp add j0hanz-filesystem-context -t stdio -c npx -a -y @j0hanz/filesystem-context-mcp
{
"mcpServers": {
"j0hanz-filesystem-context": {
"command": "npx",
"args": [
"-y",
"@j0hanz/filesystem-context-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.
- 6 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 0
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- 26 Jul 26 18
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 6 Aug 2026 · Analysed npm/@j0hanz/filesystem-context-mcp@1.0.9
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the io.github.j0hanz/filesystem-context MCP server?
io.github.j0hanz/filesystem-context is an MCP server listed in the public MCP registry as io.github.j0hanz/filesystem-context. 🔍 Read-only MCP server for secure filesystem exploration, searching, and analysis. This page covers its npm package (@j0hanz/filesystem-context-mcp).
Is the io.github.j0hanz/filesystem-context MCP server safe to use?
io.github.j0hanz/filesystem-context scores 0 out of 100 on VerifyMCP. 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.
Is the io.github.j0hanz/filesystem-context MCP server still maintained?
io.github.j0hanz/filesystem-context has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.