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/theYahia/yookassa-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/theyahia/yookassa-mcp/yookassa)<a href="https://agentmods.dev/mcp/theyahia/yookassa-mcp/yookassa"><img src="https://agentmods.dev/badge/mcp/theyahia/yookassa-mcp/yookassa/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/theyahia/yookassa-mcp/yookassa"><img src="https://agentmods.dev/badge/mcp/theyahia/yookassa-mcp/yookassa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yookassa 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 11d 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
{
"yookassa": {
"command": "npx",
"args": [
"-y",
"@theyahia/yookassa-mcp"
],
"env": {
"YOOKASSA_SHOP_ID": "<YOUR_SHOP_ID>",
"YOOKASSA_SECRET_KEY": "<YOUR_SECRET_KEY>"
}
}
}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.
- 11d ago First seen · 13 lines scan A cdfcc069a101
yookassa is an MCP server published in the GitHub repository theYahia/yookassa-mcp (4 stars, last pushed 8d 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
lunchmoney-mcp
MCP server for managing LunchMoney personal finances: transactions, budgets, categories, and more. Runs locally from the @akutishevsky/lunchmoney-mcp npm package. Needs 2 environment variables to run.
usaspending-gov-mcp
MCP server for USASpending.gov federal contract and award data. Runs locally from the usaspending-gov-mcp Python package.
tilda
MCP server for Tilda — website builder, page management (Russia). Runs locally from the @theyahia/tilda-mcp npm package. Needs 2 environment variables to run.
secedgar-mcp-server
Query SEC EDGAR filings, XBRL financials, and company data through MCP. STDIO & Streamable HTTP. Runs locally from the @cyanheads/secedgar-mcp-server npm package. Needs 2 environment variables to run.
robinhood-mcp
Read-only MCP server for Robinhood portfolio research. Runs locally from the robinhood-mcp Python package.
yandex-direct
MCP server for Yandex Direct — 20 tools: PPC campaigns, ad groups, ads, keywords, bids, negative keywords, statistics, balance (Russia). Rubles I/O, sandbox support. Runs locally from the @theyahia/yandex-direct-mcp npm package. Needs 1 environment variable to run.