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/heindewilde/yungle-clientsWrote 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/heindewilde/yungle-clients/yungle)<a href="https://agentmods.dev/mcp/heindewilde/yungle-clients/yungle"><img src="https://agentmods.dev/badge/mcp/heindewilde/yungle-clients/yungle/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/heindewilde/yungle-clients/yungle"><img src="https://agentmods.dev/badge/mcp/heindewilde/yungle-clients/yungle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yungle 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
{ "yungle": { "command": "npx", "args": [ "-y", "yungle-mcp" ], "env": { "YUNGLE_API_KEY": "", "YUNGLE_API_URL": "" } } }
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 · 13 lines scan A 73d0c5d7f7fb
yungle is an MCP server published in the GitHub repository heindewilde/yungle-clients (0 stars, last pushed 1mo 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
workflowy
MCP server "workflowy" as configured in mholzen/workflowy. Runs in Docker (ghcr.io/mholzen/workflowy:0.8.1). Needs 1 environment variable to run.
repl-mcp
Universal REPL session manager MCP server. Runs locally from the repl-mcp npm package.
memi
Memi is the design layer for agentic AI. Runs locally from the @memi-design/cli npm package.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
backscroll
MCP server "backscroll" as configured in soren-achebe/backscroll. Launched with https://github.com/soren-achebe/backscroll/releases/download/v0.9.3/backscroll-0.
email-mcp
IMAP/SMTP email MCP server — 47 tools, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.