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/juergenkoller-software/distill-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/juergenkoller-software/distill-mcp/distill)<a href="https://agentmods.dev/mcp/juergenkoller-software/distill-mcp/distill"><img src="https://agentmods.dev/badge/mcp/juergenkoller-software/distill-mcp/distill/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/juergenkoller-software/distill-mcp/distill"><img src="https://agentmods.dev/badge/mcp/juergenkoller-software/distill-mcp/distill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
distill 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 8d 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
{
"distill": {
"command": "/usr/local/bin/DistillMCP",
"env": {
"DISTILL_PORT": "22200",
"DISTILL_TOKEN": "<paste-from-distill-settings-api-mcp>"
}
}
}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.
- 8d ago First seen · 9 lines scan A d799d413c883
distill is an MCP server published in the GitHub repository juergenkoller-software/distill-mcp (2 stars, last pushed 3mo 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
hermes
MCP server "hermes", hosted remotely at localhost, as configured in pangtongya/hermes-mcp-server. Needs 1 environment variable to run.
mcp-codedoc
MCP server "mcp-codedoc" as configured in Akshay1018/mcp-codedoc. Runs locally from the mcp-codedoc Python package.
mcpspend
Query your MCPSpend usage: cost today, top tools, recent sessions, budget projections. Runs locally from the @mcpspend/mcp-server npm package. Needs 2 environment variables to run.
nodejs-api-docs
An MCP Server for Node.js API documentation. Runs locally from the mcp-server-nodejs-api-docs npm package.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.
fast-mcp-telegram
Multi-tenant Telegram gateway for AI agents — HTTP+stdio transport, 8 agent-optimized tools, MTProto User API. Runs locally from the fast-mcp-telegram Python package. Needs 4 environment variables to run.