Yandex Wordstat MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 142 installs a week from npm. Last commit 1 Nov 2026.
MCP server for Yandex Wordstat API: top & related queries, demand dynamics and regions.
What the code does
We read the source, 22 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
/(?<key>(?:login|password|secret|token|api[_-]?key|authorization)\s*[:=]\s*["']?|(?:bearer|basic)\s+)(?<val>[^,;]+)|[^\s,;]*(?:@|:\/\/|%3A|\p{L}\.\p{L})[^\s,;]*|(?<key2>\b(?:token|secret|password|api[_-]?key|access_token|refresh_token|client_secret)\s+)(?!(?:expired|invalid|is|…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-yandex-wordstat -e 'WORDSTAT_API_KEY=<WORDSTAT_API_KEY>' -e 'WORDSTAT_FOLDER_ID=<WORDSTAT_FOLDER_ID>' -- npx -y mcp-yandex-wordstat{
"mcpServers": {
"mcp-yandex-wordstat": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-wordstat"
],
"env": {
"WORDSTAT_API_KEY": "<WORDSTAT_API_KEY>",
"WORDSTAT_FOLDER_ID": "<WORDSTAT_FOLDER_ID>"
}
}
}
}[mcp_servers.mcp-yandex-wordstat]
command = "npx"
args = ["-y", "mcp-yandex-wordstat"]
env = { WORDSTAT_API_KEY = "<WORDSTAT_API_KEY>", WORDSTAT_FOLDER_ID = "<WORDSTAT_FOLDER_ID>" }{
"mcpServers": {
"mcp-yandex-wordstat": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-wordstat"
],
"env": {
"WORDSTAT_API_KEY": "<WORDSTAT_API_KEY>",
"WORDSTAT_FOLDER_ID": "<WORDSTAT_FOLDER_ID>"
}
}
}
}{
"servers": {
"mcp-yandex-wordstat": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-yandex-wordstat"
],
"env": {
"WORDSTAT_API_KEY": "<WORDSTAT_API_KEY>",
"WORDSTAT_FOLDER_ID": "<WORDSTAT_FOLDER_ID>"
}
}
}
}Put your own values in place of
<WORDSTAT_API_KEY> (Yandex Cloud API key for the Search API (sent as Api-Key). Treat it as a secret), <WORDSTAT_FOLDER_ID> (Yandex Cloud folder id, injected into every request body).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
WORDSTAT_LANG (Language for API responses (ru, en, ...)), WORDSTAT_API_BASE (API root host override), WORDSTAT_TIMEOUT_MS (Per-request timeout in milliseconds), WORDSTAT_MAX_RETRIES (Retries on transient errors (429, 5xx, network)).
Alternatives to Yandex Wordstat MCP
same job, measured the same wayMCP server for Yandex Webmaster API — site analytics, indexing, search queries
Unofficial Yandex Wordstat MCP server for SEO keyword research, trends, and regional interest.
MCP server for Yandex Wordstat API — keyword research for Russian/CIS markets
MCP server for Yandex.Webmaster search queries (read-only).
MCP server for Yandex.Metrica Stat API (read-only).
MCP server for Yandex Wordstat keyword frequencies (official API v2). Free Yandex Cloud Search API.
MCP server for Yandex Webmaster API: indexing, search queries, sitemaps, diagnostics, links.
MCP server for Yandex Tracker API.
Yandex Wordstat MCP — questions
Answers built from our own checks of this server.