Self-hosted MCP server for Yandex Search API v2 (web, image, generative search)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"yandex-search-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# yandex-search-mcp [По-русски → README.ru.md](README.ru.md) Self-hosted MCP server for **Yandex Search API v2**: web search, image search, and generative search (AI answer with cited sources). Built for Russian-language search (all 6 Yandex indexes: ru/com/tr/kk/be/uz), STDIO transport, fully typed tool parameters, structured output. Works with **Claude Code**, **Codex CLI**, and **opencode** (any MCP client with stdio support). ## Why The official `yandex/yandex-search-mcp-server` is a Turkish-market demo: only tr/en regions, XML parsed with regexes, a non-existent dependency pin, and a `json.loads(resp[1:-1])` hack on generative search. This server is a from-scratch replacement modeled on the structure and quality of `brave/brave-search-mcp-server`: - proper XML parsing with `defusedxml` (untrusted web content), parser written against **live API fixtures**; - typed parameters with fail-fast validation (no `body: dict`); - retries with exponential backoff on 429/5xx/network only; a unified JSON error contract; - the API key never leaks into logs or error messages (covered by tests); - image results contain URLs and metadata only — never base64 (a lesson from Brave's 2.0 breaking change); - LLM-facing tool descriptions with "when to use / when NOT to use" guidance. ## Tools | Tool | What it does | When to use | |---|---|---| | `yandex_web_search` | Classic web search: ranked documents (url, title, snippet) | The default: facts, news, research | | `yandex_image_search` | Image search by text query: URLs and metadata | Pictures, diagrams, references | | `yandex_gen_search` | One AI-synthesized answer with cited sources | Expensive/slow; only when a digest is explicitly needed | ## Getting credentials 1. [Create an API key](https://yandex.cloud/en/docs/iam/operations/authentication/manage-api-keys) for a service account with scope `yc.search-api.execute`. 2. Grant the service account the **`search-api.editor`** role on the folder. 3. Get your **Folder ID** …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.