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/xlsx-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/xlsx-editor)<a href="https://agentmods.dev/mcp/llamadrive/bengo-toolkit/xlsx-editor"><img src="https://agentmods.dev/badge/mcp/llamadrive/bengo-toolkit/xlsx-editor.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
xlsx-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 5d 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
{
"xlsx-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.
- 5d ago First seen · 9 lines scan A 9034d64f76e2
xlsx-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
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.
amazon-order-history-csv-download-mcp
MCP server "amazon-order-history-csv-download-mcp" as configured in marcusquinn/amazon-order-history-csv-download-mcp. Runs locally from the amazon-order-history-csv-download-mcp npm package.
mcp-office-excel
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 4 environment variables to run.
xlsx-tools-mcp
MCP server for accurate, structure-preserving read/write access to Excel (.xlsx) files. Runs locally from the xlsx-tools-mcp Python package. Needs 3 environment variables to run.
google-automation-mcp
Headless Google Workspace automation for AI - Apps Script, Gmail, Drive, Sheets, Calendar, Docs, Tasks, Forms. Runs locally from the google-automation-mcp Python package.
parse
Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells. Runs locally from the @ailang/parse npm package. Needs 2 environment variables to run.