Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Yandex Wordstat MCP

NPM · MCP-YANDEX-WORDSTAT · SCANNED SEP 20

MCP server for Yandex Wordstat API: top & related queries, demand dynamics and regions.

Available components

−1 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1344 tokens (~268/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Yandex Wordstat MCP server?

Yandex Wordstat MCP runs locally as an npm package, launched with npx -y mcp-yandex-wordstat. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-yandex-wordstat

# add to Claude Code
claude mcp add askads-mcp-yandex-wordstat -- npx -y mcp-yandex-wordstat
// .cursor/mcp.json
{
  "mcpServers": {
    "askads-mcp-yandex-wordstat": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-yandex-wordstat"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "askads-mcp-yandex-wordstat": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-yandex-wordstat"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add askads-mcp-yandex-wordstat -- npx -y mcp-yandex-wordstat
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "askads-mcp-yandex-wordstat": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-yandex-wordstat"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add askads-mcp-yandex-wordstat --command npx --arg -y --arg mcp-yandex-wordstat
# ~/.hermes/config.yaml
mcp_servers:
  askads-mcp-yandex-wordstat:
    command: "npx"
    args: ["-y", "mcp-yandex-wordstat"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "askads-mcp-yandex-wordstat": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-yandex-wordstat"
      ]
    }
  }
}
# add to Vellum
assistant mcp add askads-mcp-yandex-wordstat -t stdio -c npx -a -y mcp-yandex-wordstat
// mcp.json
{
  "mcpServers": {
    "askads-mcp-yandex-wordstat": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-yandex-wordstat"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/mcp-yandex-wordstat@2.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~888 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
dynamics ~260

Возвращает, как менялся спрос на фразу во времени, — ряд {date, count, share}, где share — доля от всех поисковых запросов Яндекса. Подходит для оценки сезонности и тренда. period задаёт шаг ряда (daily/weekly/monthly). fromDate/toDate ограничивают диапазон метками времени RFC3339, при этом toDate должен попадать на границу периода.

NameTypeReqDescription
devicesarrayФильтр по устройствам: любые из all, desktop, phone, tablet. Без параметра — все устройства.
fromDatestringНачало диапазона (RFC3339), например 2026-01-01T00:00:00Z.
periodstringШаг ряда. По умолчанию monthly.
phrasestringyesПоисковая фраза для анализа.
regionIdsarrayId регионов, которыми ограничить спрос, например [213] (Москва), [2] (Санкт-Петербург). Id берутся из list_regions. Без параметра — все регионы.
toDatestringКонец диапазона (RFC3339), выровненный по границе периода.

No output schema declared.

No examples provided.

list_regions ~87

Возвращает справочное дерево регионов, которые поддерживает Вордстат, — id регионов и их названия (label). Эти id подставляются в regionIds/regionMode остальных инструментов, а названия расшифровывают id регионов в их ответах. Дерево большое и стабильное: достаточно запросить его один раз и закешировать.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

raw_request ~139

Универсальный запрос: обращается напрямую к любому пути Wordstat в Yandex Cloud Search API — для эндпоинтов, у которых нет отдельного инструмента, например "v2/wordstat/topRequests". Все эндпоинты Вордстата работают методом POST; `body` отправляется как JSON (folderId подставляется автоматически).

NameTypeReqDescription
bodyobjectТело запроса в формате JSON.
methodstringHTTP-метод. Поддерживается только POST, он же по умолчанию.
pathstringyesПуть API, например "v2/wordstat/dynamics".

No output schema declared.

No examples provided.

regions ~148

Возвращает, как спрос на фразу распределён по регионам за последние 30 дней. В каждой строке — id региона, count, share и affinityIndex (>100% — интерес в регионе выше среднего, <100% — ниже). regionMode выбирает группировку: all, cities (только города) или regions (только области и субъекты). Сопоставить id регионов с названиями помогает list_regions.

NameTypeReqDescription
phrasestringyesПоисковая фраза для анализа.
regionModestringГруппировка: all (по умолчанию), cities (только города) или regions (только субъекты и области).

No output schema declared.

No examples provided.

top_requests ~254

Возвращает поисковый спрос по фразе за последние 30 дней: самые популярные запросы, которые СОДЕРЖАТ фразу (results), и семантически ПОХОЖИЕ запросы, которые могут её не содержать (associations), плюс totalCount. Подходит для подбора ключевых фраз и оценки спроса. Значения счётчиков могут приходить строками (int64). Необязательные regionIds и devices сужают выборку; numPhrases задаёт, сколько фраз вернуть (1..2000).

NameTypeReqDescription
devicesarrayФильтр по устройствам: любые из all, desktop, phone, tablet. Без параметра — все устройства.
numPhrasesintegerСколько топовых фраз вернуть (1..2000; по умолчанию 20).
phrasestringyesПоисковая фраза для анализа, например «купить велосипед».
regionIdsarrayId регионов, которыми ограничить спрос, например [213] (Москва), [2] (Санкт-Петербург). Id берутся из list_regions. Без параметра — все регионы.

No output schema declared.

No examples provided.

Common questions

What is the Yandex Wordstat MCP server?

Yandex Wordstat MCP is listed in the public MCP registry as io.github.askads/mcp-yandex-wordstat. MCP server for Yandex Wordstat API: top & related queries, demand dynamics and regions. This page covers its npm package (mcp-yandex-wordstat).

Is the Yandex Wordstat MCP server safe to use?

Yandex Wordstat MCP scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Yandex Wordstat MCP server expose?

Yandex Wordstat MCP exposes 5 tools: top_requests, dynamics, regions, list_regions, raw_request. Their descriptions and schemas cost roughly 888 tokens of context every time the server is loaded.

Is the Yandex Wordstat MCP server still maintained?

Yandex Wordstat MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Yandex Wordstat MCP server under?

Yandex Wordstat MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.