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/ellmos-ai/ellmos-clatcher-mcpWrote 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/ellmos-ai/ellmos-clatcher-mcp/ellmos-clatcher-mcp)<a href="https://agentmods.dev/mcp/ellmos-ai/ellmos-clatcher-mcp/ellmos-clatcher-mcp"><img src="https://agentmods.dev/badge/mcp/ellmos-ai/ellmos-clatcher-mcp/ellmos-clatcher-mcp/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/ellmos-ai/ellmos-clatcher-mcp/ellmos-clatcher-mcp"><img src="https://agentmods.dev/badge/mcp/ellmos-ai/ellmos-clatcher-mcp/ellmos-clatcher-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ellmos-clatcher-mcp 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 11d 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
{
"ellmos-clatcher-mcp": {
"command": "npx",
"args": [
"-y",
"ellmos-clatcher-mcp"
],
"env": {}
}
}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.
- 11d ago First seen · 10 lines scan A bbeecda9d335
ellmos-clatcher-mcp is an MCP server published in the GitHub repository ellmos-ai/ellmos-clatcher-mcp (1 stars, last pushed yesterday), 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
caldav-mcp
CalDAV calendar operations (list, create, update, delete events) as MCP tools. Runs locally from the caldav-mcp npm package. Needs 3 environment variables to run.
n8n-manager-mcp
MCP server for n8n workflow management -- view, create, sync and manage workflows via AI. Runs locally from the n8n-manager-mcp npm package.
vibe-mcp
Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers. Runs locally from the slashvibe-mcp npm package.
componecat
Software component catalog: search your org's services, docs, APIs, dependencies, and ownership. Runs locally from the @shaftware/componecat-mcp npm package.
mcp-react-toolkit
9 MCP servers for React/TypeScript — dep auditing, a11y, test gen, and TypeScript enforcement. Runs locally from the mcp-react-toolkit npm package.
vdiff-mcp
Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes. Runs locally from the vdiff-mcp npm package. Needs 1 environment variable to run.