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/seyka-ai/yandex-tools-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/seyka-ai/yandex-tools-mcp/yandex-search)<a href="https://agentmods.dev/mcp/seyka-ai/yandex-tools-mcp/yandex-search"><img src="https://agentmods.dev/badge/mcp/seyka-ai/yandex-tools-mcp/yandex-search/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/seyka-ai/yandex-tools-mcp/yandex-search"><img src="https://agentmods.dev/badge/mcp/seyka-ai/yandex-tools-mcp/yandex-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yandex-search 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- yandex-search — 100% identical, 0 lines differ
- yandex-search — 100% identical, 0 lines differ
What it actually says
{
"yandex-search": {
"command": "node",
"args": [
"--env-file=.env",
"packages/yandex-search-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.
- 11d ago First seen · 9 lines scan A a54d97a0c7f5
yandex-search is an MCP server published in the GitHub repository seyka-ai/yandex-tools-mcp (70 stars, last pushed 11d 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-10-28.
yandex-search compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| yandex-searchseyka-ai/yandex-tools-mcp | MCP server | 70 | 11d ago | MIT | A | — | Claude Code |
| yandex-direct-mcpstufently/yandex-mcp | MCP server | 20 | 2d ago | MIT | A | — | Claude Code |
| yandex-search-mcpstufently/yandex-mcp | MCP server | 20 | 2d ago | MIT | A | — | Claude Code |
| yandex-wordstat-mcpstufently/yandex-mcp | MCP server | 20 | 2d ago | MIT | A | — | Claude Code |
| yandex-metrika-mcpstufently/yandex-mcp | MCP server | 20 | 2d ago | MIT | A | — | Claude Code |
| yandex-webmaster-mcpstufently/yandex-mcp | MCP server | 20 | 2d ago | MIT | A | — | Claude Code |
| kd-scoutmoiosintel/kd-scout | MCP server | 0 | 2mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |