Yandex Webmaster (weselow) MCP Server

yandex-webmaster-mcp-server npm v1.0.0

Published by weselow — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP-сервер для Yandex Webmaster API v4 — 46 инструментов для управления сайтами через Model Context Protocol

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 46

Each tool and what it can reach — statically extracted from the published source.

  • ywm_get_search_events_samplesingests untrusted input
  • ywm_add_hostno sensitive capability
  • ywm_add_original_textno sensitive capability
  • ywm_add_sitemapno sensitive capability
  • ywm_batch_add_feedsno sensitive capability
  • ywm_batch_remove_feedsno sensitive capability
  • ywm_delete_hostno sensitive capability
  • ywm_delete_original_textno sensitive capability
  • ywm_delete_sitemapno sensitive capability
  • ywm_get_broken_internal_linksno sensitive capability
Show 36 more tools ↓
  • ywm_get_broken_links_historyno sensitive capability
  • ywm_get_diagnosticsno sensitive capability
  • ywm_get_external_linksno sensitive capability
  • ywm_get_external_links_historyno sensitive capability
  • ywm_get_feed_upload_statusno sensitive capability
  • ywm_get_hostno sensitive capability
  • ywm_get_host_summaryno sensitive capability
  • ywm_get_important_urlsno sensitive capability
  • ywm_get_important_urls_historyno sensitive capability
  • ywm_get_indexing_historyno sensitive capability
  • ywm_get_indexing_samplesno sensitive capability
  • ywm_get_original_text_quotano sensitive capability
  • ywm_get_original_textsno sensitive capability
  • ywm_get_popular_queriesno sensitive capability
  • ywm_get_query_historyno sensitive capability
  • ywm_get_recrawl_quotano sensitive capability
  • ywm_get_recrawl_taskno sensitive capability
  • ywm_get_search_events_historyno sensitive capability
  • ywm_get_search_queriesno sensitive capability
  • ywm_get_search_urlsno sensitive capability
  • ywm_get_search_urls_historyno sensitive capability
  • ywm_get_sitemapno sensitive capability
  • ywm_get_sqi_historyno sensitive capability
  • ywm_get_userno sensitive capability
  • ywm_get_user_sitemapno sensitive capability
  • ywm_get_verificationno sensitive capability
  • ywm_list_feedsno sensitive capability
  • ywm_list_hostsno sensitive capability
  • ywm_list_ownersno sensitive capability
  • ywm_list_recrawl_tasksno sensitive capability
  • ywm_list_sitemapsno sensitive capability
  • ywm_list_user_sitemapsno sensitive capability
  • ywm_query_analyticsno sensitive capability
  • ywm_start_feed_uploadno sensitive capability
  • ywm_submit_recrawlno sensitive capability
  • ywm_verify_hostno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/yandex-webmaster-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/yandex-webmaster-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/yandex-webmaster-mcp-server"><img src="https://mcptrustchecker.com/registry/yandex-webmaster-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/yandex-webmaster-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan yandex-webmaster-mcp-server --online

Use the free API → How scoring works

Other implementations of Yandex Webmaster 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Web, Search & Scraping