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/rubyLs/yearning_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/rubyls/yearning_mcp/yearning-mcp)<a href="https://agentmods.dev/mcp/rubyls/yearning_mcp/yearning-mcp"><img src="https://agentmods.dev/badge/mcp/rubyls/yearning_mcp/yearning-mcp/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/rubyls/yearning_mcp/yearning-mcp"><img src="https://agentmods.dev/badge/mcp/rubyls/yearning_mcp/yearning-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yearning-mcp 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 2mo 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
{ "yearning-mcp": { "command": "npx", "args": [ "-y", "@rubyls/yearning-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.
- 2mo ago First seen · 9 lines scan A 253b6f269ec7
yearning-mcp is an MCP server published in the GitHub repository rubyLs/yearning_mcp (2 stars, last pushed 2mo 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.
yearning-mcp compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| yearning-mcprubyLs/yearning_mcp | MCP server | 2 | 2mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| quilt-mcpquiltdata/quilt-mcp-server | MCP server | 3 | 3d ago | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mssql-mcp-serverc0h1b4/mssql-mcp-server | MCP server | 15 | 1mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| sql-server-mcpahaugerud/sql-server-mcp | MCP server | 0 | 9d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| elastic-mcpcsimi/elastic-mcp | MCP server | 1 | 2mo ago | ISC | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-database-serveroliverhubtech-source/mcp-database-server | MCP server | 0 | 2mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-opensearchbunnyiesart/mcp-opensearch | MCP server | 0 | 2mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |