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/mjdevaccount/AIStack-MCPWrote 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/mjdevaccount/aistack-mcp/filesystem)<a href="https://agentmods.dev/mcp/mjdevaccount/aistack-mcp/filesystem"><img src="https://agentmods.dev/badge/mcp/mjdevaccount/aistack-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/mjdevaccount/aistack-mcp/filesystem"><img src="https://agentmods.dev/badge/mcp/mjdevaccount/aistack-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 20d 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.
This is a copy
86% identical to filesystem — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"C:\\AIStack-MCP"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 20d ago First seen · 10 lines scan A 9f079c5d0ff3
filesystem is an MCP server published in the GitHub repository mjdevaccount/AIStack-MCP (2 stars, last pushed 3d 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. It is 86% identical to filesystem, differing in 2 lines, and is treated as a copy.
Other mcp servers, from other repositories
moira
MCP server "moira" as configured in moira-mcp/moira. Runs in Docker (ghcr.io/moira-mcp/moira:0.3.4).
unifi
MCP server "unifi" as configured in pete-builds/mcp-unifi. Runs in Docker (ghcr.io/pete-builds/mcp-unifi:0.5.1). Needs 9 environment variables to run.
mnemo-mcp
Open-source MCP Server for persistent AI memory with embedded sync. Runs locally from the mnemo-mcp Python package. Needs 1 environment variable to run.
n8n-fabric
MCP server "n8n-fabric" as configured in ry-ops/n8n-fabric. Runs locally from the n8n-fabric Python package.
local-mcp-toolbox
MCP server "local-mcp-toolbox" as configured in chriswayneh/local-mcp-toolbox. Launched with ${LOCAL_MCP_TOOLBOX_EXE} serve --config ${LOCAL_MCP_TOOLBOX_CONFIG}.
qmd-mcp
MCP server "qmd-mcp" as configured in X1pheR/qmd-mcp. Runs in Docker (ghcr.io/x1pher/qmd-mcp:v0.1.3).