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/tradecatlabs/fatecatWrote 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/tradecatlabs/fatecat/clients-horosa)<a href="https://agentmods.dev/mcp/tradecatlabs/fatecat/clients-horosa"><img src="https://agentmods.dev/badge/mcp/tradecatlabs/fatecat/clients-horosa/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/tradecatlabs/fatecat/clients-horosa"><img src="https://agentmods.dev/badge/mcp/tradecatlabs/fatecat/clients-horosa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
horosa 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
{
"horosa": {
"command": "uv",
"args": [
"run",
"--directory",
"<PATH_TO_REPO>/horosa-skill",
"horosa-skill",
"serve",
"--transport",
"stdio"
],
"cwd": "<PATH_TO_REPO>/horosa-skill"
}
}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 · 15 lines scan A cb2281a9784a
horosa is an MCP server published in the GitHub repository tradecatlabs/fatecat (202 stars, last pushed 2mo 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-30.
Other mcp servers, from other repositories
geo-optimizer
MCP server "geo-optimizer" as configured in Auriti-Labs/geo-optimizer-skill. Launched with .venv/bin/geo-mcp. Needs 1 environment variable to run.
graft
MCP server "graft" as configured in Auriti-Labs/geo-optimizer-skill. Launched with graft mcp.
technocore-chat
MCP server for technocore-chat: shared rooms, durable notes and rendezvous for agents, over plain HTTP. Runs locally from the technocore-mcp Python package. Needs 2 environment variables to run.
counsel-mcp
MCP server "counsel-mcp", hosted remotely at liki.hk, as configured in ml8s/liki.
engine-mcp
MCP server "engine-mcp", hosted remotely at liki.hk, as configured in ml8s/liki.
seo-geo-mcp-server
Audit a page's SEO and its readiness for AI answer engines: meta, schema, robots, sitemaps, AI bots. Runs locally from the seo-geo-mcp-server npm package.