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/BumpyClock/file-tools-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/bumpyclock/file-tools-mcp/file-tools-mcp)<a href="https://agentmods.dev/mcp/bumpyclock/file-tools-mcp/file-tools-mcp"><img src="https://agentmods.dev/badge/mcp/bumpyclock/file-tools-mcp/file-tools-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/bumpyclock/file-tools-mcp/file-tools-mcp"><img src="https://agentmods.dev/badge/mcp/bumpyclock/file-tools-mcp/file-tools-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
file-tools-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 1mo 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
{ "file-tools-mcp": { "command": "uvx", "args": [ "file-tools-mcp" ] } }
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.
- 1mo ago First seen · 8 lines scan A d1519d48f77d
file-tools-mcp is an MCP server published in the GitHub repository BumpyClock/file-tools-mcp (0 stars, last pushed 1y 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
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package. Needs 1 environment variable to run.
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.
email-mcp
IMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.
sendgrid-mcp
MCP server for SendGrid's v3 API: email marketing, transactional mail, templates, and analytics. Runs locally from the sendgrid-mcp npm package. Needs 2 environment variables to run.
root-mcp
Production-grade MCP server for CERN ROOT file analysis. Runs locally from the root-mcp Python package.
web-access
The most accurate web access API. Stop getting blocked. Runs locally from the @usestring/mcp npm package. Needs 1 environment variable to run.