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.
npx agentmods add mcp/configflux/weld/agent-graph-demo-filesystemgit clone --depth 1 https://github.com/configflux/weldWrote 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/configflux/weld/agent-graph-demo-filesystem)<a href="https://agentmods.dev/mcp/configflux/weld/agent-graph-demo-filesystem"><img src="https://agentmods.dev/badge/mcp/configflux/weld/agent-graph-demo-filesystem.svg" alt="Measured on agentmods" 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 6d 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": {
"description": "Local repository file context."
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. 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.
- 6d ago First seen · 5 lines scan A 1041285c009a
filesystem is an MCP server published in the GitHub repository configflux/weld (6 stars, last pushed 3d ago), licensed Apache-2.0. 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
astra-code-context
MCP server "astra-code-context" as configured in nimelkot/astra. Runs locally from the astra-code-context Python package.
sem
Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents. Runs locally from the @ataraxy-labs/sem npm package.
gograph
MCP server "gograph" as configured in ozgurcd/gograph. Launched with https://github.com/ozgurcd/gograph/releases/download/v1.6.8/gograph_1.6.8_darwin.
agent-lsp
Stateful LSP runtime for AI agents — 50+ tools across 30+ languages via MCP. Runs locally from the @blackwell-systems/agent-lsp npm package.
code-index
Rust code index MCP server, native 1C:Enterprise (BSL) support. 32 tools, AST for 14 languages. Runs locally from the @regsorm/code-index-mcp npm package.
m1nd
MCP server "m1nd" as configured in maxkle1nz/m1nd. Launched with m1nd-mcp --stdio --no-gui. Needs 1 environment variable to run.