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)<a href="https://agentmods.dev/mcp/sdebruyn/fabric-dw-mcp-cli/fabric-dw"><img src="https://agentmods.dev/badge/mcp/sdebruyn/fabric-dw-mcp-cli/fabric-dw/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"><img src="https://agentmods.dev/badge/mcp/sdebruyn/fabric-dw-mcp-cli/fabric-dw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fabric-dw 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 10d 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": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"fabric-dw@latest",
"fabric-dw-mcp"
],
"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.
- 10d ago First seen · 12 lines scan A 017c2ba52887
fabric-dw is an MCP server published in the GitHub repository sdebruyn/fabric-dw-mcp-cli (10 stars, last pushed today), 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
qdrant-search
MCP server "qdrant-search", hosted remotely, as configured in nick-pape/grackle.
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.
rag-db-advisor
MCP server "rag-db-advisor" as configured in kenimo49/rag-db-advisor. Runs locally from the rag-db-advisor Python package.
haiku-rag
Local-first agentic RAG with citations - hybrid search, reranking and multimodal retrieval over your own documents, no database server required. Runs locally from the haiku-rag Python 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.
mcp-neo4j-knowledge-graph
Neo4j-based knowledge graph MCP server with temporal versioning and semantic search. Runs locally from the @henrychong-ai/mcp-neo4j-knowledge-graph npm package.