Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/fieldcure/fieldcure-mcp-filesystemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/fieldcure/fieldcure-mcp-filesystem/mcp-filesystem)<a href="https://agentmods.dev/mcp/fieldcure/fieldcure-mcp-filesystem/mcp-filesystem"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-filesystem/mcp-filesystem/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/fieldcure/fieldcure-mcp-filesystem/mcp-filesystem"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-filesystem/mcp-filesystem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
filesystem scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"filesystem": {
"command": "FieldCure.Mcp.Filesystem",
"args": [],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 7 lines scan A 36c9ec874545
filesystem is an MCP server published in the GitHub repository fieldcure/fieldcure-mcp-filesystem (1 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-workspace
MCP server "mcp-workspace" as configured in MarcusJellinghaus/mcp-workspace. Launched with ${MCP_CODER_VENV_PATH}\mcp-workspace.exe --project-dir ${MCP_CODER_PROJECT_DIR} . Needs 1 environment variable to run.
mcp-tools-py
MCP server "mcp-tools-py" as configured in MarcusJellinghaus/mcp-workspace. Launched with ${MCP_CODER_VENV_PATH}\mcp-tools-py.exe --project-dir ${MCP_CODER_PROJECT_DIR} -. Needs 1 environment variable to run.
obsidian-wiki
MCP server "obsidian-wiki" as configured in MarcusJellinghaus/mcp-workspace. Launched with cmd /c npx -y obsidian-mcp ${USERPROFILE}\Documents\GitHub\obsidian-dev-wiki.
filesystem-mcp
Secure filesystem MCP server for reading, writing, searching, diffing, and patching files. Runs locally from the @j0hanz/filesystem-mcp npm package. Needs 1 environment variable to run.
ellmos-filecommander-mcp
Filesystem MCP server: files, processes, sessions, async search, OCR, archives, safe delete. Runs locally from the ellmos-filecommander-mcp npm package.
mcp-synology
MCP server for Synology NAS — manage files on your NAS via Claude. Runs locally from the mcp-synology Python package.