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/askads/mcp-yandex-wordstatWrote 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/plugins/askads/mcp-yandex-wordstat/plugin)<a href="https://agentmods.dev/plugins/askads/mcp-yandex-wordstat/plugin"><img src="https://agentmods.dev/badge/plugins/askads/mcp-yandex-wordstat/plugin/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/plugins/askads/mcp-yandex-wordstat/plugin"><img src="https://agentmods.dev/badge/plugins/askads/mcp-yandex-wordstat/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-yandex-wordstat 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 9d 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.
What it actually says
{
"name": "mcp-yandex-wordstat",
"displayName": "Yandex Wordstat MCP",
"version": "2.3.1",
"description": "Read Yandex search-demand statistics from Claude: how often a phrase is searched, when, and in which regions.",
"author": {
"name": "gistrec",
"url": "https://gistrec.cloud"
},
"homepage": "https://github.com/askads/mcp-yandex-wordstat#readme",
"repository": "https://github.com/askads/mcp-yandex-wordstat",
"license": "MIT",
"privacyPolicyUrl": "https://askads.ru/privacy-policy",
"keywords": [
"yandex-wordstat",
"keyword-research",
"seo",
"marketing"
],
"userConfig": {
"token": {
"type": "string",
"title": "Yandex Cloud API key",
"description": "API key with access to the Yandex Cloud Search API. Stored in your operating system's credential store, never in settings.json.",
"sensitive": true,
"required": true
},
"folder_id": {
"type": "string",
"title": "Yandex Cloud folder id",
"description": "Folder the API key belongs to. Required: a key pointed at the wrong folder returns 401 or 403.",
"required": true
},
"telemetry": {
"type": "string",
"title": "Anonymous telemetry",
"description": "Set to 0 to disable the anonymous usage telemetry the server sends by default. Leave as 1 to keep it on.",
"default": "1"
}
},
"mcpServers": {
"yandex-wordstat": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"WORDSTAT_API_KEY": "${user_config.token}",
"WORDSTAT_FOLDER_ID": "${user_config.folder_id}",
"ASKADS_TELEMETRY": "${user_config.telemetry}"
}
}
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 0 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 56 lines scan A 6547666ce378
mcp-yandex-wordstat is a plugin published in the GitHub repository askads/mcp-yandex-wordstat (7 stars, last pushed 9d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-04.
Other plugins, from other repositories
hasdata-google-trends-mcp
Google Trends MCP server for Cursor. Interest over time, interest by region, and rising and top related queries and topics for any keyword, as structured JSON. Remote MCP server hosted by HasData, connects over streamable HTTP with your HasData API key.
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
mc-agent-toolkit
Monte Carlo Agent Toolkit — data observability skills and enforcement hooks for AI coding agents.
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.
mosaic-bridge
Mosaic Bridge — Unity MCP assistant agents for scene building, shader creation, and session continuity.
collate
A plugin that provides an end-to-end workflow for OCR and proofreading historical Chinese documents. OCR turns scanned page images into editable text.