io.github.BoxLab-Ltd/yandex-webmaster-mcp
NPM · @BOXLAB/YANDEX-WEBMASTER-MCP · SCANNED SEP 20
Query Yandex Webmaster indexing, queries, diagnostics and backlinks, and recrawl, via an AI agent.
Available components
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 & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to BoxLab-Ltd/yandex-webmaster-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1646 tokens (~164/item across 10 items; 10 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 Management93
- Stability observed for 28 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the io.github.BoxLab-Ltd/yandex-webmaster-mcp server?
io.github.BoxLab-Ltd/yandex-webmaster-mcp runs locally as an npm package, launched with npx -y @boxlab/yandex-webmaster-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @boxlab/yandex-webmaster-mcp
claude mcp add boxlab-ltd-yandex-webmaster-mcp -- npx -y @boxlab/yandex-webmaster-mcp
{
"mcpServers": {
"boxlab-ltd-yandex-webmaster-mcp": {
"command": "npx",
"args": [
"-y",
"@boxlab/yandex-webmaster-mcp"
]
}
}
} {
"servers": {
"boxlab-ltd-yandex-webmaster-mcp": {
"command": "npx",
"args": [
"-y",
"@boxlab/yandex-webmaster-mcp"
]
}
}
} codex mcp add boxlab-ltd-yandex-webmaster-mcp -- npx -y @boxlab/yandex-webmaster-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"boxlab-ltd-yandex-webmaster-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@boxlab/yandex-webmaster-mcp"
],
"enabled": true
}
}
} openclaw mcp add boxlab-ltd-yandex-webmaster-mcp --command npx --arg -y --arg @boxlab/yandex-webmaster-mcp
mcp_servers:
boxlab-ltd-yandex-webmaster-mcp:
command: "npx"
args: ["-y", "@boxlab/yandex-webmaster-mcp"] {
"McpServers": {
"boxlab-ltd-yandex-webmaster-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@boxlab/yandex-webmaster-mcp"
]
}
}
} assistant mcp add boxlab-ltd-yandex-webmaster-mcp -t stdio -c npx -a -y @boxlab/yandex-webmaster-mcp
{
"mcpServers": {
"boxlab-ltd-yandex-webmaster-mcp": {
"command": "npx",
"args": [
"-y",
"@boxlab/yandex-webmaster-mcp"
]
}
}
} 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.
- 20 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.
- 18 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 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.
- 11 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.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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/@boxlab/yandex-webmaster-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | BoxLab-Ltd/yandex-webmaster-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/BoxLab-Ltd/yandex-webmaster-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 2212244571 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:041c0f1ca9bc5e3ae0836e16a2e26e0cdbc2fab04edf99028d207492373bf24cd6ba283879d1294d9c6e555de8432ff4aa777e72558ccf5c5ec55b78a |
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 →
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 →
get_diagnostics Site diagnostics ~150
Yandex Webmaster site diagnostics: problems detected on the host (e.g. DNS errors, slow response, robots.txt issues, 4xx alerts), each with a severity (FATAL, CRITICAL, POSSIBLE_PROBLEM, RECOMMENDATION). By default returns only ACTIVE problems (state=PRESENT), worst first. Set includeAbsent=true to also list resolved/absent problem types. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| hostId | string | – | Host id (e.g. "https:example.com:443"). Defaults to YANDEX_WEBMASTER_HOST_ID. List valid ids with get_hosts. |
| includeAbsent | boolean | – | Also list problem types that are currently absent/resolved. Default false. |
No output schema declared.
No examples provided.
get_external_links External links ~159
Inbound (external) links pointing to the host — the backlinks Yandex knows. Read-only. • report="samples" (default): example links with source page, target URL and discovery date, plus the total count available. • report="history": time series of the total external-link count over time.
| Name | Type | Req | Description |
|---|---|---|---|
| hostId | string | – | Host id (e.g. "https:example.com:443"). Defaults to YANDEX_WEBMASTER_HOST_ID. |
| limit | integer | – | report="samples": rows to return (1-100). Default 20. |
| offset | integer | – | report="samples": rows to skip for paging. Default 0. |
| report | string | – | Which report to return. Default "samples". |
No output schema declared.
No examples provided.
get_hosts List Webmaster hosts ~127
Discovery tool: list the sites (hosts) available to your Yandex Webmaster token, each with its host_id, URL and verification state. host_id is what every other tool needs to identify a site. Optionally pass `hostId` to also fetch that host summary (SQI, indexed/excluded page counts, site problems). Read-only. Call this first.
| Name | Type | Req | Description |
|---|---|---|---|
| hostId | string | – | Optional host id (e.g. "https:example.com:443"). When set, the response also includes that host summary. Defaults to YANDEX_WEBMASTER_HOST_ID if configured. |
No output schema declared.
No examples provided.
get_indexing Site indexing ~228
How Yandex crawls and indexes the host. Read-only. Pick a report: • report="history" (default): time series of crawled pages grouped by HTTP status class (HTTP_2XX/3XX/4XX/5XX/OTHER) — spot spikes of errors the crawler hits. • report="crawled": example crawled URLs with their HTTP code and crawl date. • report="in_search": example URLs currently present in Yandex search, with title.
| Name | Type | Req | Description |
|---|---|---|---|
| dateFrom | string | – | report="history": start date YYYY-MM-DD. |
| dateTo | string | – | report="history": end date YYYY-MM-DD. |
| hostId | string | – | Host id (e.g. "https:example.com:443"). Defaults to YANDEX_WEBMASTER_HOST_ID. |
| limit | integer | – | samples reports: rows to return (1-100). Default 20. |
| offset | integer | – | samples reports: rows to skip for paging. Default 0. |
| report | string | – | Which report to return. Default "history". |
No output schema declared.
No examples provided.
list_sitemaps List sitemaps ~121
List the Sitemap files Yandex knows for the host, each with its URL, type, last access date, number of URLs and error count, and where it was discovered (robots.txt, webmaster, etc.). Use it to check a sitemap is being read and is error-free. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| hostId | string | – | Host id (e.g. "https:example.com:443"). Defaults to YANDEX_WEBMASTER_HOST_ID. |
| limit | integer | – | Max sitemaps to return (1-100). Default 100. |
No output schema declared.
No examples provided.
login Sign in to Yandex ~108
Sign in to Yandex from here. Opens your browser to approve access; the code returns automatically over a local redirect, so this usually finishes in one call. If the local port is unavailable it returns a URL to approve and you then call submit_code with the code Yandex shows. Run this once (the token lasts ~1 year); needed before the data tools if you are not signed in yet.
| Name | Type | Req | Description |
|---|---|---|---|
| oob | boolean | – | Force the copy-paste flow instead of the automatic local redirect. |
No output schema declared.
No examples provided.
recrawl_status Recrawl quota & tasks ~156
Read-only view of the host recrawl activity. With no taskId: the remaining daily quota plus the most recent recrawl tasks and their state (IN_PROGRESS, DONE, FAILED). Pass taskId (from recrawl_submit) to check one task. Use before recrawl_submit to confirm quota is available.
| Name | Type | Req | Description |
|---|---|---|---|
| hostId | string | – | Host id (e.g. "https:example.com:443"). Defaults to YANDEX_WEBMASTER_HOST_ID. |
| limit | integer | – | Recent tasks to list when no taskId (1-100). Default 10. |
| taskId | string | – | Check a single recrawl task by its id (from recrawl_submit). Omit to get quota + recent tasks. |
No output schema declared.
No examples provided.
recrawl_submit Submit URL for recrawl ~145
Ask Yandex to recrawl a specific page of the host sooner. NOT read-only: each call consumes one unit of the limited daily recrawl quota (check it with recrawl_status). The URL must belong to the host and be a full absolute URL. Returns the task_id and the remaining quota. Track progress with recrawl_status using the returned task_id.
| Name | Type | Req | Description |
|---|---|---|---|
| hostId | string | – | Host id (e.g. "https:example.com:443"). Defaults to YANDEX_WEBMASTER_HOST_ID. |
| url | string | yes | Absolute URL of the page to recrawl, e.g. "https://example.com/page/". Must belong to the host. |
No output schema declared.
No examples provided.
search_queries Yandex search queries ~402
Search-query analytics for a host from Yandex Search: impressions (TOTAL_SHOWS), clicks (TOTAL_CLICKS), average show/click position. Read-only. • report="top" (default): ranked list of the queries bringing the most traffic, ordered by orderBy. Use this to see which phrases people search. • report="trend": a time series. Pass queryId (from a prior "top" call) for one query's history over time, or omit it for the site's aggregate trend. Tip: cross-reference these queries/landing pages with Yandex Metrica (bounce rate, conversions) to find high-impression, low-conversion phrases worth optimizing.
| Name | Type | Req | Description |
|---|---|---|---|
| dateFrom | string | – | Start date, YYYY-MM-DD. Default: last week. |
| dateTo | string | – | End date, YYYY-MM-DD. Default: today. |
| deviceType | string | – | Device bucket. Default ALL. |
| hostId | string | – | Host id (e.g. "https:example.com:443"). Defaults to YANDEX_WEBMASTER_HOST_ID. List valid ids with get_hosts. |
| indicators | array | – | Which indicators to return. Default: all four (TOTAL_SHOWS, TOTAL_CLICKS, AVG_SHOW_POSITION, AVG_CLICK_POSITION). |
| limit | integer | – | report="top" only: rows to return (1-500). Default 50. |
| offset | integer | – | report="top" only: rows to skip for paging. Default 0. |
| orderBy | string | – | report="top" only: rank by TOTAL_SHOWS or TOTAL_CLICKS. Default TOTAL_CLICKS. |
| queryId | string | – | report="trend" only: return the time series for this specific query (query_id from a prior "top" call). Omit for the aggregate trend. |
| report | string | – | "top" ranked list (default) or "trend" time series. |
No output schema declared.
No examples provided.
submit_code Submit the Yandex sign-in code ~50
Complete a copy-paste sign-in started by login: pass the code Yandex showed you after you approved access.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code shown on the Yandex page after you approved access. |
No output schema declared.
No examples provided.
What is the io.github.BoxLab-Ltd/yandex-webmaster-mcp server?
io.github.BoxLab-Ltd/yandex-webmaster-mcp is listed in the public MCP registry as io.github.BoxLab-Ltd/yandex-webmaster-mcp. Query Yandex Webmaster indexing, queries, diagnostics and backlinks, and recrawl, via an AI agent. This page covers its npm package (@boxlab/yandex-webmaster-mcp).
Is the io.github.BoxLab-Ltd/yandex-webmaster-mcp server safe to use?
io.github.BoxLab-Ltd/yandex-webmaster-mcp scores 94 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. Its build provenance is signed and verified. 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 io.github.BoxLab-Ltd/yandex-webmaster-mcp server expose?
io.github.BoxLab-Ltd/yandex-webmaster-mcp exposes 10 tools: login, submit_code, get_hosts, search_queries, get_indexing, and 5 more. Their descriptions and schemas cost roughly 1,646 tokens of context every time the server is loaded.
Is the io.github.BoxLab-Ltd/yandex-webmaster-mcp server still maintained?
io.github.BoxLab-Ltd/yandex-webmaster-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 io.github.BoxLab-Ltd/yandex-webmaster-mcp server under?
io.github.BoxLab-Ltd/yandex-webmaster-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.