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-webmasterWrote 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-webmaster/plugin)<a href="https://agentmods.dev/plugins/askads/mcp-yandex-webmaster/plugin"><img src="https://agentmods.dev/badge/plugins/askads/mcp-yandex-webmaster/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-webmaster/plugin"><img src="https://agentmods.dev/badge/plugins/askads/mcp-yandex-webmaster/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-yandex-webmaster 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 6d 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-webmaster",
"displayName": "Yandex Webmaster MCP",
"version": "1.1.2",
"description": "Work with Yandex Webmaster from Claude: site indexing, search-query analytics, sitemaps, diagnostics, external links and recrawl requests.",
"author": {
"name": "gistrec",
"url": "https://gistrec.cloud"
},
"homepage": "https://github.com/askads/mcp-yandex-webmaster#readme",
"repository": "https://github.com/askads/mcp-yandex-webmaster",
"license": "MIT",
"privacyPolicyUrl": "https://askads.ru/privacy-policy",
"keywords": [
"yandex-webmaster",
"seo",
"indexing",
"search-console"
],
"userConfig": {
"token": {
"type": "string",
"title": "Yandex OAuth token",
"description": "OAuth token for the Yandex Webmaster API. Stored in your operating system's credential store, never in settings.json.",
"sensitive": true,
"default": ""
},
"user_id": {
"type": "string",
"title": "Yandex user id",
"description": "Webmaster user id the token belongs to. Leave empty to resolve it from the token.",
"default": ""
},
"host_id": {
"type": "string",
"title": "Default host id",
"description": "Host to use when a request does not name one, for example https:example.com:443.",
"default": ""
},
"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-webmaster": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"YANDEX_OAUTH_TOKEN": "${user_config.token}",
"YANDEX_USER_ID": "${user_config.user_id}",
"YANDEX_WEBMASTER_HOST_ID": "${user_config.host_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 — 35 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.
- 6d ago First seen · 63 lines scan A 04eac3f635ee
mcp-yandex-webmaster is a plugin published in the GitHub repository askads/mcp-yandex-webmaster (0 stars, last pushed 6d 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-05.
Other plugins, from other repositories
yandex-metrica-mcp
MCP server for Yandex Metrica — query your web analytics in plain language. Secretless PKCE login, read-only, TypeScript.
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
usercall
AI-moderated voice and text interviews with real users. Learn why users churn or drop off in onboarding, and get themes, insights, and verbatim quotes. Research triggers invite users after an in-product moment.
n8n-pro-mcp marketplace
Full-instance management for self-hosted n8n (incl. queue mode): workflows, executions, tags, credentials, variables, projects, users, audit and health — 51 tools.
vibsync-mcp
Long-term team memory and live work context for AI coding agents.
mcp-yandex-audience
An MCP server that lets an AI application work with Yandex Audiences, Yandex's advertising-audience service. It can create customer and lookalike segments, and manage pixels and access settings.