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/stufently/yandex-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/stufently/yandex-mcp/yandex-webmaster)<a href="https://agentmods.dev/mcp/stufently/yandex-mcp/yandex-webmaster"><img src="https://agentmods.dev/badge/mcp/stufently/yandex-mcp/yandex-webmaster/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/stufently/yandex-mcp/yandex-webmaster"><img src="https://agentmods.dev/badge/mcp/stufently/yandex-mcp/yandex-webmaster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yandex-webmaster 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 10d 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
{
"yandex-webmaster": {
"command": "node",
"args": [
"--env-file=.env",
"packages/yandex-webmaster-mcp/src/index.mjs"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 10d ago First seen · 9 lines scan A 3f86856ce142
yandex-webmaster is an MCP server published in the GitHub repository stufently/yandex-mcp (18 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-30.
Other mcp servers, from other repositories
kd-scout
MCP server "kd-scout" as configured in moiosintel/kd-scout. Runs locally from the kd-scout Python package.
rankoracle
SEO Intelligence MCP — 13 tools: keyword research, SERP, domain audits, competitors. Remote server at tooloracle.io.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
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.
claude-octopus
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. Runs locally from the claude-octopus npm package. Needs 7 environment variables to run.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.