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/llamadrive/bengo-toolkit/docx-editorgit clone --depth 1 https://github.com/llamadrive/bengo-toolkitWrote 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/llamadrive/bengo-toolkit/docx-editor)<a href="https://agentmods.dev/mcp/llamadrive/bengo-toolkit/docx-editor"><img src="https://agentmods.dev/badge/mcp/llamadrive/bengo-toolkit/docx-editor.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
docx-editor 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 3d 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-editor": {
"command": "npx",
"args": [
"-y",
"@knorq/[email protected]"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 3d ago First seen · 9 lines scan A 9c103a8f86ce
docx-editor is an MCP server published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo 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
adeu
Automated DOCX Redlining Engine. Runs locally from the @adeu/mcp-server npm package.
excel-csv-mcp-server
🚀 The Ultimate Data Science MCP Server - Advanced statistical analysis, ML preprocessing, and data visualization for Excel & CSV files. Runs locally from the excel-csv-mcp-server npm package.
moxie-docs
MCP server "moxie-docs", hosted remotely at moxiedocs.com, as configured in Jackalope-Dev/Moxie-Docs-MCP.
mcp-itglue
IT Glue MCP server for MSPs — documents, flexible assets, semantic vector search, RBAC, and BYOK. Runs locally from the mcp-itglue npm package. Needs 9 environment variables to run.
mcp-google-docs
MCP server for the Google Docs API: read and edit documents, styles, tables, images, comments. Runs locally from the @a1-x-tech/mcp-google-docs npm package. Needs 8 environment variables to run.
openwarrant
Document forensics: tamper/AI checks, fields, tables, identity, screening, tenders, citations. Remote server at www.stipple.sh.