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/mdfifty50-boop/docx-forge-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/mdfifty50-boop/docx-forge-mcp/docx-forge)<a href="https://agentmods.dev/mcp/mdfifty50-boop/docx-forge-mcp/docx-forge"><img src="https://agentmods.dev/badge/mcp/mdfifty50-boop/docx-forge-mcp/docx-forge/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/mdfifty50-boop/docx-forge-mcp/docx-forge"><img src="https://agentmods.dev/badge/mcp/mdfifty50-boop/docx-forge-mcp/docx-forge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
docx-forge 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 8d 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
{
"docx-forge": {
"command": "npx",
"args": [
"-y",
"docx-forge-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.
- 8d ago First seen · 10 lines scan A 0217b5900d53
docx-forge is an MCP server published in the GitHub repository mdfifty50-boop/docx-forge-mcp (0 stars, last pushed 4mo 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-server-excel
MCP server "mcp-server-excel" as configured in sbroenne/mcp-server-excel. Launched with Sbroenne.ExcelMcp.McpServer.
mcp-documentation-server
Local-first document management and semantic search for AI coding agents. Runs locally from the @andrea9293/mcp-documentation-server npm package.
adeu
MCP server "adeu" as configured in dealfluence/adeu. Runs locally from the adeu-server Python package.
nutrient-document-engine-mcp-server
MCP server for self-hosted Nutrient Document Engine: extract, edit, redact, and annotate documents. Runs locally from the @nutrient-sdk/document-engine-mcp-server npm package. Needs 5 environment variables to run.
better-notion-mcp
Markdown-first MCP server for Notion API with 8 composite tools and 39 actions. Runs locally from the @n24q02m/better-notion-mcp npm package. Needs 1 environment variable to run.
itglue-mcp
MCP server "itglue-mcp" as configured in WYRE-AI/itglue-mcp. Runs in Docker (ghcr.io/wyre-ai/itglue-mcp:v1.16.5). Needs 6 environment variables to run.