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/mariusei/file-scanner-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/mariusei/file-scanner-mcp/scantool)<a href="https://agentmods.dev/mcp/mariusei/file-scanner-mcp/scantool"><img src="https://agentmods.dev/badge/mcp/mariusei/file-scanner-mcp/scantool.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
scantool 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 7d 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
{ "scantool": { "command": "uvx", "args": [ "scantool" ] } }
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.
- 7d ago First seen · 8 lines scan A 7424c00e992d
scantool is an MCP server published in the GitHub repository mariusei/file-scanner-mcp (3 stars, last pushed 3d 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
socraticode
SocratiCode — MCP server for local codebase indexing, semantic search, and code dependency graphs. All private, all local via Docker. Runs locally from the socraticode npm package.
code-index
Rust code index MCP server, native 1C:Enterprise (BSL) support. 32 tools, AST for 14 languages. Runs locally from the @regsorm/code-index-mcp npm package.
parecode
Token-aware ripgrep code search and atomic multi-file edits for coding agents. Runs locally from the parecode npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
devlens
Query a precomputed code graph (nodes, edges, summaries) of TS/JS/React/Next.js/Node repos via MCP. Runs locally from the @devlensio/cli npm package.
project-graph-mcp
MCP server for AI agents — project graph, code quality analysis, visual web explorer. JS, TS, Python, Go. Runs locally from the project-graph-mcp npm package.