Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Yandex Webmaster is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
33
tools declared
local
runs on your machine
—
downloads a day
What it does
MCP server for Yandex Webmaster API — site analytics, indexing, search queries
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'YANDEX_WEBMASTER_TOKEN=${YANDEX_WEBMASTER_TOKEN}' --transport stdio stufently-yandex-webmaster-mcp '--' npx -y @stufently/yandex-webmaster-mcp
# 2 — ask your agent for something these tools do
# get-user, list-hosts, get-host and 30 more
It needs YANDEX_WEBMASTER_TOKEN: this reads it from your environment, so export it first.
Yandex Webmaster costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 19 servers
stufently19 servers
6 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Yandex Webmaster as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads YANDEX_WEBMASTER_TOKEN (OAuth token for Yandex Webmaster) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx YANDEX_WEBMASTER_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'YANDEX_WEBMASTER_TOKEN=${YANDEX_WEBMASTER_TOKEN}' --transport stdio stufently-yandex-webmaster-mcp '--' npx -y @stufently/yandex-webmaster-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: YANDEX_WEBMASTER_TOKEN — OAuth token for Yandex Webmaster. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
33 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get current Webmaster user info and user_id.
No parameter schema on file.
List all hosts (sites) in Webmaster with their host_id — the identifier every other tool
No parameter schema on file.
Get details for a specific host.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID (URL-encoded, e.g. "https:example.com:443") |
Get site summary: SQI, pages count, problems.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
Get SQI (Site Quality Index) history over time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| date_from | string | no | Start date YYYY-MM-DD |
| date_to | string | no | End date YYYY-MM-DD |
Get site diagnostics. Text lists problems in state PRESENT (code, severity, date); full response is in structuredContent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
Get popular search queries for a site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| order_by | string | yes | Sort by shows or clicks |
| device_type | string | no | Device filter |
| date_from | string | no | Start date YYYY-MM-DD |
| date_to | string | no | End date YYYY-MM-DD |
| limit | integer | no | Results limit (default: 100) |
| offset | integer | no | Offset |
Get search query totals history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| device_type | string | no | — |
| date_from | string | no | — |
| date_to | string | no | — |
Get indexing history over time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| date_from | string | no | — |
| date_to | string | no | — |
Get sample indexed URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | — |
| offset | integer | no | — |
Get in-search (appearing in results) history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| date_from | string | no | — |
| date_to | string | no | — |
Get sample URLs appearing in search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | — |
| offset | integer | no | — |
Get search URL events history (appeared/removed).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| date_from | string | no | — |
| date_to | string | no | — |
Get sample URLs for search events (appeared in / removed from search), with the reason each
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| event_type | string | no | Keep only events of this type (client-side filter; omit to get both) |
| limit | integer | no | Limit (default: 10) |
| offset | integer | no | — |
Pages DROPPED FROM SEARCH inside a time window, with the reason for each one (url +
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | How many EXCLUDED pages to collect (default: 20) |
| offset | integer | no | Event-stream offset to resume from (default: 0) |
| max_requests | integer | no | — |
| returned_urls | array | no | — |
Get external links pointing to the site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | — |
| offset | integer | no | — |
Get external links count history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| date_from | string | no | — |
| date_to | string | no | — |
List broken internal links (destination URL, the source page linking to it, and when Yandex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | — |
| offset | integer | no | — |
Get broken internal links count history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| date_from | string | no | — |
| date_to | string | no | — |
List all sitemaps for a host.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | — |
Get details for a specific sitemap.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| sitemap_id | string | yes | Sitemap ID (URL-encoded) |
Add a Sitemap file to Yandex Webmaster (user-added sitemaps). Returns sitemap_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | — |
Get important URLs for a site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| limit | integer | no | — |
| offset | integer | no | — |
Get history for a specific important URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| url | string | yes | URL to get history for |
| date_from | string | no | — |
| date_to | string | no | — |
Enqueue a URL for Yandex re-crawl. Daily quota applies (check get-recrawl-quota). Returns task_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
List recrawl queue for a host (URLs submitted via add-recrawl-url with their state).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID (e.g. "https:example.com:443") |
| limit | integer | no | Max results (default 10) |
| offset | integer | no | Pagination offset |
Add a new site (host) to Yandex Webmaster. The host_url must include protocol (e.g. "https://example.com"). After adding, the host needs verification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID |
| task_id | string | yes | Recrawl task ID |
Start the Yandex Webmaster ownership check for a host. Put the verification_uin (see verify-host)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID (URL-encoded, e.g. "https:example.com:443") |
Remove a host (site) from Yandex Webmaster. IRREVERSIBLE: verification, indexing and search-query history,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_id | string | yes | Host ID (URL-encoded, e.g. "https:example.com:443") |
| confirm | boolean | no | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Yandex Webmaster or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 2.2.1 · scanned 16 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings2 threat · 10 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digestdfce820c3f1ee3f675dc9813d901136070942ddad3f3d84a133e2be314358ddb
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (33 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
33 of the 33 recovered tools are registered only when command === 'auth' is false (src/index.mjs:31) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
No tool is registered unconditionally · 33 only when command === 'auth' is false (src/index.mjs:31) — typically when a key or option is configured. All 33 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get-user conditional | no tags | |
| list-hosts conditional | no tags | |
| get-host conditional | no tags | |
| get-summary conditional | no tags | |
| get-sqi-history conditional | no tags | |
| get-diagnostics conditional | no tags | |
| get-popular-queries conditional | no tags | |
| get-query-history conditional | no tags | |
| get-indexing-history conditional | no tags | |
| get-indexing-samples conditional | no tags | |
| get-insearch-history conditional | no tags | |
| get-insearch-samples conditional | no tags | |
| get-search-events-history conditional | no tags | |
| get-search-events-samples conditional | no tags | |
| get-excluded-pages conditional | no tags | |
| get-external-links conditional | no tags | |
| get-external-links-history conditional | no tags | |
| get-broken-internal-links conditional | no tags | |
| get-broken-internal-links-history conditional | no tags | |
| get-sitemaps conditional | no tags | |
| get-sitemap conditional | no tags | |
| get-user-sitemaps conditional | no tags | |
| get-important-urls conditional | no tags | |
| get-important-url-history conditional | no tags | |
| get-recrawl-quota conditional | untrusted-input | untrusted-input: keyword "crawl", parameter "url" with "crawl" in the description |
| get-recrawl-queue conditional | no tags | |
| get-recrawl-task conditional | no tags | |
| verify-host conditional | no tags | |
| delete-host conditional | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| add-sitemap conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| add-recrawl-url conditional | untrusted-inputexternal-sink | untrusted-input: keyword "crawl", parameter "url" with "crawl" in the description; external-sink: declares readOnlyHint: false, openWorldHint: true |
| add-host conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| start-verification conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestdfce820c3f1ee3f6
Scanned2026-10-16
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.2.1. Pin a release below and the command asks for exactly that one.
2.2.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Yandex Webmaster can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.