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/rog0x/mcp-lint-toolsWrote 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/rog0x/mcp-lint-tools/lint)<a href="https://agentmods.dev/mcp/rog0x/mcp-lint-tools/lint"><img src="https://agentmods.dev/badge/mcp/rog0x/mcp-lint-tools/lint/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/rog0x/mcp-lint-tools/lint"><img src="https://agentmods.dev/badge/mcp/rog0x/mcp-lint-tools/lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lint 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.
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.
- 1mo ago First seen · 10 lines scan A 08b23055d291
lint is an MCP server published in the GitHub repository rog0x/mcp-lint-tools (0 stars, last pushed 7mo 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
prodlint
Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance. Runs locally from the prodlint npm package.
codesentinel-mcp
Codebase health MCP: dead code, cycles, coupling, architectural drift. Runs locally from the @cubiczan/codesentinel-mcp npm package.
safe-fix-mcp
MCP server: finds real dead code (vulture + deptry) and proposes a branch+PR for the one class safe to auto-remove -- unused imports on a single-name line -- gated on a real full test-suite pass. A human still merges. Runs locally from the safe-fix-mcp Python package.
zapier-dev-mcp
For Zapier integration developers: inspect, lint, and validate zapier-platform-cli projects. Runs locally from the zapier-dev-mcp npm package.
leakguard-mcp
Squawk for backtests — static leakage/lookahead-bias detector for trading/ML strategy code, exposed over MCP. Runs locally from the leakguard-mcp Python package.
ovecc
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate. Runs locally from the ovecc npm package.