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/cloro-dev/mcp-serverWrote 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/cloro-dev/mcp-server/cloro)<a href="https://agentmods.dev/mcp/cloro-dev/mcp-server/cloro"><img src="https://agentmods.dev/badge/mcp/cloro-dev/mcp-server/cloro/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/cloro-dev/mcp-server/cloro"><img src="https://agentmods.dev/badge/mcp/cloro-dev/mcp-server/cloro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cloro 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.
What it actually says
{
"cloro": {
"url": "https://mcp.cloro.dev/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A b648861905e8
cloro is an MCP server published in the GitHub repository cloro-dev/mcp-server (0 stars, last pushed 6d 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
refd
Read AI search visibility, competitors, citations, prompts, and answer evidence from refd. Remote server at api.refd.ai.
developers-mcp
Access Mastercard Developers APIs, documentation, and API specifications through MCP. Runs locally from the @mastercard/developers-mcp npm package.
digestseo-geo
Self-hostable MCP server for AI visibility tracking across ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews. Free OSS with an optional EUR 99 one-time AI Visibility Audit for teams that want a client-ready baseline. Runs locally from the @digestseo/mcp-geo npm package.
mcp-geo
Track brand citations across five AI search engines. Free OSS; optional EUR 99 client-ready audit. Runs locally from the @digestseo/mcp-geo npm package.
mcp-server
350+ production-ready APIs through one MCP server — weather, geocoding, validation, financial data. Remote server at api.apiverve.com.
geo-tool-check
Is this page readable for AI search? Checks crawler access, structure and citability for ChatGPT, Perplexity, Claude and Google AI. CLI and MCP server, runs entirely on your machine. Runs locally from the geo-tool-check npm package.