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/cooldk/clize-cliWrote 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/cooldk/clize-cli/sites)<a href="https://agentmods.dev/mcp/cooldk/clize-cli/sites"><img src="https://agentmods.dev/badge/mcp/cooldk/clize-cli/sites/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/cooldk/clize-cli/sites"><img src="https://agentmods.dev/badge/mcp/cooldk/clize-cli/sites.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sites 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 15d 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
{ "sites": { "command": "npx", "args": [ "-y", "@clize/sites", "@clize/sites", "clize-mcp" ], "env": {} } }
What else
This page is one entry in a file that holds 5. 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.
- 15d ago First seen · 12 lines scan A fd97f920514b
sites is an MCP server published in the GitHub repository cooldk/clize-cli (0 stars, last pushed 16d 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-10-02.
Other mcp servers, from other repositories
domain-intelligence
WHOIS, DNS records, SSL certificate data for any domain in one call. x402. Remote server at domain-intelligence.api.klymax402.com.
hostinger-mcp-server
The most complete MCP server for Hostinger — 280+ tools, OAuth, HTTP transport, retry/cache, batch operations, deploy automation. Runs locally from the hostinger-mcp-server npm package.
globodai-mcp-gandi
MCP server "globodai-mcp-gandi" as configured in globodai-group/mcp-gandi. Runs locally from the globodai-mcp-gandi npm package.
globodai-mcp-gcloud-dns
MCP server "globodai-mcp-gcloud-dns" as configured in globodai-group/mcp-gcloud-dns. Runs locally from the globodai-mcp-gcloud-dns npm package.
globodai-mcp-cloudflare-dns
MCP server "globodai-mcp-cloudflare-dns" as configured in globodai-group/mcp-cloudflare-dns. Runs locally from the globodai-mcp-cloudflare-dns npm package.
k8s-mcp-server
MCP server "k8s-mcp-server" as configured in VersusControl/devops-ai-guidelines. Launched with ${workspaceFolder}/code/04/bin/k8s-mcp-server.