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/homespunapps/homespunWrote 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/homespunapps/homespun/mcp-homespun)<a href="https://agentmods.dev/mcp/homespunapps/homespun/mcp-homespun"><img src="https://agentmods.dev/badge/mcp/homespunapps/homespun/mcp-homespun/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/homespunapps/homespun/mcp-homespun"><img src="https://agentmods.dev/badge/mcp/homespunapps/homespun/mcp-homespun.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
homespun 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 10d 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
{
"homespun": {
"command": "npx",
"args": [
"-y",
"@homespunapps/mcp"
],
"env": {
"HOMESPUN_API_KEY": "",
"HOMESPUN_URL": "",
"HOMESPUN_AGENT_NAME": "",
"HOMESPUN_REGISTER_SECRET": ""
}
}
}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.
- 10d ago First seen · 15 lines scan A 52fdd2d8f835
homespun is an MCP server published in the GitHub repository homespunapps/homespun (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
memoire
MCP server "memoire" as configured in memi-design/memi. Launched with memi --profile locked mcp start --no-figma.
memi
Memi is the design layer for agentic AI. Runs locally from the @memi-design/cli npm package.
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.
rrt
MCP server "rrt" as configured in Anselmoo/mcp-zen-of-languages. Runs locally from the repo-release-tools[mcp] Python package.
analyzer
MCP server for Python, JavaScript, and TypeScript code analysis with Ruff, ty, Vulture, and Biome. Runs locally from the mcp-server-analyzer Python package.
zoom-agent-cli
CLI and MCP server for the Zoom API — built for humans and AI agents. Runs locally from the zoom-agent-cli npm package.