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/houtini-ai/fanout-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/houtini-ai/fanout-mcp/fanout)<a href="https://agentmods.dev/mcp/houtini-ai/fanout-mcp/fanout"><img src="https://agentmods.dev/badge/mcp/houtini-ai/fanout-mcp/fanout/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/houtini-ai/fanout-mcp/fanout"><img src="https://agentmods.dev/badge/mcp/houtini-ai/fanout-mcp/fanout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fanout 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
{
"fanout": {
"command": "npx",
"args": [
"-y",
"@houtini/fanout-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 250142986667
fanout is an MCP server published in the GitHub repository houtini-ai/fanout-mcp (12 stars, last pushed 4mo ago), licensed Apache-2.0. 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
zotero-mcp
A Model Context Protocol server for Zotero. Runs locally from the zotero-mcp-server Python package. Needs 5 environment variables to run.
obsidian-hybrid-search
Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval. Runs locally from the obsidian-hybrid-search npm package. Needs 10 environment variables to run.
veritasgraph
The first zero-trust, air-gapped Enterprise GraphRAG server for the Model Context Protocol (MCP). Runs locally from the veritasgraph-mcp Python package. Needs 3 environment variables to run.
developers-mcp
Access Mastercard Developers APIs, documentation, and API specifications through MCP. Runs locally from the @mastercard/developers-mcp npm package.
vectr
Semantic codebase search + persistent working memory for AI code editors. Local, zero-config, MCP. No API key. Runs locally from the vectr Python package.
midjourney-mcp
A MCP server for generating images with Midjourney. Runs locally from the midjourney-mcp Python package.