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/Mangomunchr/farpy-publicWrote 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/mangomunchr/farpy-public/farpy)<a href="https://agentmods.dev/mcp/mangomunchr/farpy-public/farpy"><img src="https://agentmods.dev/badge/mcp/mangomunchr/farpy-public/farpy/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/mangomunchr/farpy-public/farpy"><img src="https://agentmods.dev/badge/mcp/mangomunchr/farpy-public/farpy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
farpy 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 9d 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
{ "farpy": { "url": "https://api.farpy.com/mcp", "type": "sse" } }
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.
- 9d ago First seen · 6 lines scan A 194691794a07
farpy is an MCP server published in the GitHub repository Mangomunchr/farpy-public (1 stars, last pushed 5d 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
ai-game-studio-blender
MCP server "ai-game-studio-blender" as configured in frabcd/codex-ai-game-studio. Runs ${PLUGIN_ROOT}/scripts/mcp_adapter.py with python. Needs 1 environment variable to run.
ellmos-blender-use-mcp
Headless Blender asset QA over MCP: background script runs and FBX reimport verification. Runs locally from the ellmos-blender-use-mcp npm package.
mcp-producer
MCP Server for Producer AI Music Generation via AceDataCloud API. Runs locally from the mcp-producer Python package. Needs 1 environment variable to run.
mcp-flux-pro
MCP Server for Flux AI Image Generation via AceDataCloud API. Runs locally from the mcp-flux-pro Python package. Needs 1 environment variable to run.
ldraw-mcp
MCP server that renders LDraw/LEGO models to images with real part geometry via headless Blender + ImportLDraw. Runs locally from the ldraw-mcp Python package. Needs 2 environment variables to run.
theory-mcp
Chords, scales, progressions, transposition, and MIDI tools for music theory AI agents. Runs locally from the @playbykey/theory-mcp npm package.