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/iloveitaly/llm-ide-rulesWrote 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/iloveitaly/llm-ide-rules/chrome-mcp-server)<a href="https://agentmods.dev/mcp/iloveitaly/llm-ide-rules/chrome-mcp-server"><img src="https://agentmods.dev/badge/mcp/iloveitaly/llm-ide-rules/chrome-mcp-server/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/iloveitaly/llm-ide-rules/chrome-mcp-server"><img src="https://agentmods.dev/badge/mcp/iloveitaly/llm-ide-rules/chrome-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chrome-mcp-server 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 3d 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
{
"chrome-mcp-server": {
"url": "http://127.0.0.1:12306/mcp"
}
}What else mcp.json configures
This page is one entry in a file that holds 7. 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.
- 3d ago First seen · 5 lines scan A 89e309422173
chrome-mcp-server is an MCP server published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed 2d 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-09-06.
Other mcp servers, from other repositories
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
mintlify-docs
MCP server "mintlify-docs", hosted remotely at www.mintlify.com, as configured in nottelabs/notte.
notte-docs
MCP server "notte-docs", hosted remotely at docs.notte.cc, as configured in nottelabs/notte.
weapp-agent-mcp
Agent-first MCP server for WeChat Mini Program debugging & automation via WeChat DevTools. Runs locally from the @chaixueyuan/weapp-agent-mcp npm package. Needs 15 environment variables to run.
core
Agent-native MCP server for driving, inspecting, and asserting on real Electron desktop apps. Runs locally from the @electron-stagewright/core npm package.
playwright
MCP server "playwright" as configured in chrisdothtml/ai-job-finder. Launched with yarn dlx @playwright/mcp@latest.