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/sdebruyn/fabric-dw-mcp-cliWrote 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/sdebruyn/fabric-dw-mcp-cli/fabric-dw-mcp)<a href="https://agentmods.dev/mcp/sdebruyn/fabric-dw-mcp-cli/fabric-dw-mcp"><img src="https://agentmods.dev/badge/mcp/sdebruyn/fabric-dw-mcp-cli/fabric-dw-mcp/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/sdebruyn/fabric-dw-mcp-cli/fabric-dw-mcp"><img src="https://agentmods.dev/badge/mcp/sdebruyn/fabric-dw-mcp-cli/fabric-dw-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fabric-dw-mcp 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 12d 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
{
"fabric-dw-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/sdebruyn/fabric-dw:2026.8.0"
],
"env": {
"FABRIC_AUTH": "default",
"FABRIC_MCP_READONLY": "",
"FABRIC_MCP_ALLOW_DESTRUCTIVE": "",
"FABRIC_MCP_WORKSPACES": "",
"FABRIC_MCP_ALLOW_REMOTE": "",
"FABRIC_LOG_LEVEL": "INFO"
}
}
}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.
- 12d ago First seen · 19 lines scan A 74802c1a3121
fabric-dw-mcp is an MCP server published in the GitHub repository sdebruyn/fabric-dw-mcp-cli (10 stars, last pushed 2d 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
koncept-mcp-server
Query a curated YAML semantic concept graph for codebase invariants and cross-cutting facts. Runs locally from the @yourtechtribe-labs/koncept-mcp-server npm package.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
dbeast
MCP server "dbeast" as configured in snss10/DBeast. Runs ${workspaceFolder}/dbeast/src/server.py with python. Needs 9 environment variables to run.
tierline
MCP server "tierline" as configured in jayj221/tierline. Runs locally from the tierline npm package.
socialgo
Model Context Protocol server for SocialGO — lets AI assistants (Claude, etc.) search services and place SMM orders, including keyless guest checkout (buy without an account, no API key). Runs locally from the @socialgo/mcp npm package. Needs 3 environment variables to run.
warehouse-mcp
Production MCP server for Postgres, Oracle, Snowflake, BigQuery, Redshift, DuckDB, MotherDuck. Runs locally from the warehouse-mcp npm package. Needs 19 environment variables to run.