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/clubpay/ronykitWrote 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/clubpay/ronykit/ronyup)<a href="https://agentmods.dev/mcp/clubpay/ronykit/ronyup"><img src="https://agentmods.dev/badge/mcp/clubpay/ronykit/ronyup/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/clubpay/ronykit/ronyup"><img src="https://agentmods.dev/badge/mcp/clubpay/ronykit/ronyup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ronyup 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 yesterday.
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
{
"ronyup": {
"command": "ronyup",
"args": [
"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.
- yesterday First seen · 8 lines scan A bd96f70abe68
ronyup is an MCP server published in the GitHub repository clubpay/ronykit (38 stars, last pushed 2d ago), licensed BSD-3-Clause. 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-09-07.
Other mcp servers, from other repositories
chassis-mcp
Scaffold an Express 5 + TypeScript backend: database, auth, optional Next.js front end. Runs locally from the chassis-mcp npm package.
contact-verifier
MCP server "contact-verifier" as configured in owieschon/contact-verifier. Runs locally from the contact-verifier Python package.
mcpify
CLI tool that generates an MCP server from OpenAPI specs automatically. Runs locally from the @bahridev/mcpify npm package.
asuswrt-mcp
Local MCP server for controlled AsusWRT and AsusWRT-Merlin router administration. Runs locally from the asuswrt-mcp Python package. Needs 5 environment variables to run.
wordpress-mcp
Lightweight WordPress MCP server - 42 tools, token-optimized (95% smaller responses). Runs locally from the @cavort-it-systems/wordpress-mcp npm package. Needs 3 environment variables to run.
receipts-api
MCP server "receipts-api" as configured in chf3198/receipts-api-mcp. Runs locally from the receipts-api Python package.