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/YohannHommet/repo-lens-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/yohannhommet/repo-lens-mcp/repo-lens-mcp)<a href="https://agentmods.dev/mcp/yohannhommet/repo-lens-mcp/repo-lens-mcp"><img src="https://agentmods.dev/badge/mcp/yohannhommet/repo-lens-mcp/repo-lens-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/yohannhommet/repo-lens-mcp/repo-lens-mcp"><img src="https://agentmods.dev/badge/mcp/yohannhommet/repo-lens-mcp/repo-lens-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
repo-lens-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 11d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 11d ago First seen · 9 lines scan A 13ea238b4b31
repo-lens-mcp is an MCP server published in the GitHub repository YohannHommet/repo-lens-mcp (0 stars, last pushed 5mo ago), with no licence file. 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-cisco-support
MCP server for Cisco Support APIs including Bug Search and future tools. Runs locally from the mcp-cisco-support npm package.
xident-dev
Xident build-time MCP server — docs lookup, sandbox test verifications, webhook debugging. Runs locally from the @xident/mcp-dev npm package. Needs 1 environment variable to run.
mcp-queue-doctor
Diagnoses pg-boss and graphile-worker job queues: retry storms, stuck workers, missed schedules. Runs locally from the mcp-queue-doctor npm package.
tieline
Static FE-BE contract-drift checker: finds frontend calls the backend does not expose. CLI + MCP. Runs locally from the @nugehs/tieline npm package.
mnehmos.trace.mcp
MCP server for detecting producer/consumer schema mismatches with multi-language support. Runs locally from the mnehmos.trace.mcp npm package.
django-mcp-inspector
An MCP server that exposes Django runtime information to AI agents. Runs locally from the django-mcp-inspector Python package.