
Yandex Per Result
io.github.johnisanerdPublished by GitHub account johnisanerdv1.0.0Updated Nov 3, 2026
Yandex rank tracking and bulk SERP data, billed per result, hosted MCP.
Overview
Yandex Per Result's hosted MCP server (mcp.apify.com); OAuth sign-in required; Streamable HTTP.
No AI overview yet: these facts come from the registry entry and the server itself.
- Endpoint
- mcp.apify.com
- Last checked
Installation
In SourceWeft
- Open Yandex Per Result in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.johnisanerd%2Fyandex-per-result/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"yandex-per-result": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/yandex-scrape-yandex-search-results-at-scale---per-result"
}
}
}README
English | Русский
🔍 Yandex Search API: Search Results in Clean JSON, Billed Per Page
One flat fee per page of results, every result type included. The developer-friendly way to use the Yandex Search API.
Actor page: apify.com/johnvc/yandex-scrape-yandex-search-results-at-scale---per-result Input schema: apify.com/johnvc/yandex-scrape-yandex-search-results-at-scale---per-result/input-schema
This Yandex Search API bills a one-time Search Start fee per run plus a flat fee per page of results, so cost scales with the number of pages you fetch, not with how many result types you enable. It queries Yandex, the dominant search engine across Russia and several Eastern European and Central Asian markets, and returns clean, structured JSON, one item per result type per page. Each item carries the search parameters, result counts, and arrays for organic results, ads, knowledge graph, inline images, and inline videos. Supports regional domains, language and region targeting, and pagination.
This Actor was originally billed per result and keeps "per-result" in its URL and this repo name so existing links keep working. It now bills per page, at the same prices as our other Yandex listing, Scrape Yandex.
Video Walkthrough
Quick Start
Prerequisites
- Python 3.11 or higher
- An Apify account and API key (get a free key here)
-
Clone the repository
-
Install dependencies with UV
-
Configure your API key
-
Run the example
Alternative: set the API key directly
Why Use This Yandex Search API?
One price per page. A page is billed once however many result types it returns, and a page that returns nothing for your selection is not billed, which suits exploratory research, keyword testing, and workloads where result density varies between queries.
An independent search index. Yandex maintains its own web index with distinct rankings, regional content, and Cyrillic-language coverage not replicated elsewhere. For Russian-language research, Eastern European markets, or comparative SEO, it is a unique source.
Multi-domain support. Target yandex.ru, yandex.com, yandex.com.tr, yandex.by, yandex.kz, and yandex.uz, then combine with lang and lr for precise control over the regional index and language variant.
Rich result types. Beyond organic results, each page returns ads, knowledge graph entries, inline image blocks, and inline video carousels in one structured output.
Predictable, pay-per-use pricing. Billing is per page plus a one-time Search Start fee per run, with no subscription, and the max_pages cap keeps cost under your control.
Easy to automate. Call it from Python in a few lines, or load it as an MCP tool so assistants like Claude and Cursor can run Yandex searches for you on demand.
Features
Core Capabilities
- Yandex search across 6 supported regional domains
- A la carte result types: toggle organic, ads, knowledge graph, inline images, and inline videos independently; enabling more types does not raise the per-page price
- Language and region control with
langandlr - Sort and recency filters:
sort_mode(relevance or date) andperiod(all, day, last_two_weeks, month) - Parallel multi-page pagination with a configurable
max_pagescap - Per-page billing: one Search Start fee per run, then a flat fee per page delivered
Data Quality
- One item per result type per page, tagged with
item_typeandresult_count organic_resultsarray with position, title, link, snippet, and displayed link- Result counts and metadata echoed on every item
- Separate arrays for ads, knowledge graph, images, and videos
- Consistent JSON shape across every query
Usage Examples
Basic search
Regional domain with language and region targeting
Input Parameters
Output Format
Each selected result type present on a page is returned as its own dataset item, tagged with item_type (organic, ads, knowledge_graph, inline_images, or inline_videos) and a result_count; each item is billed as one result. A representative organic item for machine learning tutorial is shown below (the organic_results array is trimmed to a single result here).
Each page item echoes the search parameters and result counts, lists every organic listing in organic_results (with position, title, link, snippet, and displayed link; video and news results may also include duration and date), and returns separate ads_results, knowledge_graph, inline_images, and inline_videos arrays.
Use as an MCP tool
You can load the Yandex Search API as an MCP tool so assistants call it for you. The MCP server URL preloads just this one Actor:
Authenticate with OAuth in the browser when offered, or with your Apify API token (the same APIFY_API_TOKEN used by the Python example). Get a token at https://console.apify.com/settings/integrations and a free Apify account at https://apify.com?fpr=9n7kx3 .
Install in Claude Cowork Desktop
[Install in Claude Cowork Desktop]
Cowork is the desktop app's automation mode. To give it the Yandex Search API as a tool, add the Apify MCP server as a connector.
- Open the Claude desktop app and go to Settings → Connectors (or Settings → Developer → Edit Config to edit
claude_desktop_config.jsondirectly).- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Add the Apify MCP server, preloaded with only this Actor:
- Restart the app. When Cowork first calls the tool, complete the OAuth prompt in your browser, or add your Apify API token in the connector settings to skip OAuth.
- In a Cowork chat, confirm the tool is available and ask it to run the Yandex Search API.
Download the desktop app and start a free trial: https://claude.ai/referral/uIlpa7nPLg More help: https://docs.apify.com/platform/integrations/claude-desktop
Install in Claude Code
Claude Code is the command-line tool. Add the Actor's MCP server with one command:
To use a token instead of browser OAuth:
Then verify with claude mcp list, or run /mcp inside a session. Ask Claude Code to call the Yandex Search API.
Try Claude Code free: https://claude.ai/referral/uIlpa7nPLg Claude Code MCP docs: https://code.claude.com/docs/en/mcp
Install in Claude (website)
On claude.ai you add Apify as a connector, then enable just this Actor's tool.
- Go to Settings → Connectors → Browse connectors and search for Apify MCP server. Install it (enable or update if prompted).
- When connecting, authenticate with your Apify API token, and enable the tool
johnvc/yandex-scrape-yandex-search-results-at-scale---per-result. - In any chat, open + → Connectors and turn on Apify.
- Alternatively, choose Add custom connector and paste the full MCP URL
https://mcp.apify.com/?tools=actors,docs,johnvc/yandex-scrape-yandex-search-results-at-scale---per-result, using OAuth when prompted. - Ask Claude to run the Yandex Search API.
Open Claude on the web: https://claude.ai/referral/uIlpa7nPLg
Install in Cursor
Cursor reads MCP servers from a project file at .cursor/mcp.json.
- In your project, create
.cursor/mcp.json:
- If you prefer token auth over browser OAuth, add a header:
- Open Cursor → Settings → MCP and confirm the apify server is connected (green dot).
- In Composer or Chat, ask Cursor to call the Yandex Search API.
New to Cursor? Get it here: https://cursor.com/referral?code=XQP4VBLI3NNX
Install in ChatGPT
ChatGPT connects to the Apify MCP server through Developer mode (available on ChatGPT Pro, Plus, Business, Enterprise, and Education plans).
- Click your profile icon, then go to Settings > Apps. If you do not see a Create app button, open Advanced settings and enable Developer mode.
- Click Create app and fill out the form:
- Name: Apify
- MCP Server URL:
https://mcp.apify.com/?tools=actors,docs,johnvc/yandex-scrape-yandex-search-results-at-scale---per-result - Authentication: OAuth
- Click Create and authorize the connection with Apify.
- To use the app in a conversation, click + in the chat, choose Developer mode, and select Apify.
More help: https://docs.apify.com/platform/integrations/mcp
Use the Yandex Search API to power SEO research, market intelligence, and multilingual content analysis with reliable, structured results.
Featured Tasks
Ready-to-run examples on the Apify Store.
🤖 Ask an AI assistant about this Actor
Open a ready-to-send prompt about the Yandex Search API in the AI of your choice:
- 💬 ChatGPT
- 🧠 Claude
- 🔍 Perplexity
- 🅒 Copilot
Last Updated: 2026.10.27
Source: README.md at commit 7596c0e
Tools
0Version history
1- v1.0.0LatestNov 3, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.