@stufently/yandex-webmaster-mcp

MCPcommunity
v2.2.0stufentlyMITUpdated 1d agonpmGitHub

MCP server for Yandex Webmaster API — site analytics, indexing, search queries

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
18GitHub stars
1Forks
1d agoLast update
Needs 1 credential before it runs
  • YANDEX_WEBMASTER_TOKENAPI keyrequired

    OAuth token for Yandex Webmaster

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorstufently
LicenseMIT
Version2.2.0
Sourcenpm+mcp-registry
npm@stufently/yandex-webmaster-mcp
GitHubstufently/yandex-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface29 tools · 1 privileged
Security scan✓ Cleanv2.2.0 · 1d agoHow well does this scan work?
EvalsNone
IndexedOct 15, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

29 tools · 1 privileged
Statically extracted from the published packagev2.2.0 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get-userGet current Webmaster user info and user_id.

Get current Webmaster user info and user_id.

No input schema was published for this tool.

list-hostsList all hosts (sites) in Webmaster with their host_id — the identifier every other tool

List all hosts (sites) in Webmaster with their host_id — the identifier every other tool

No input schema was published for this tool.

get-hostGet details for a specific host.

Get details for a specific host.

No input schema was published for this tool.

get-summaryGet site summary: SQI, pages count, problems.

Get site summary: SQI, pages count, problems.

No input schema was published for this tool.

get-sqi-historyGet SQI (Site Quality Index) history over time.

Get SQI (Site Quality Index) history over time.

No input schema was published for this tool.

get-diagnosticsGet site diagnostics. Text lists problems in state PRESENT (code, severity, date); full response is in structuredContent.

Get site diagnostics. Text lists problems in state PRESENT (code, severity, date); full response is in structuredContent.

No input schema was published for this tool.

get-popular-queriesGet popular search queries for a site.

Get popular search queries for a site.

No input schema was published for this tool.

get-query-historyGet search query totals history.

Get search query totals history.

No input schema was published for this tool.

get-indexing-historyGet indexing history over time.

Get indexing history over time.

No input schema was published for this tool.

get-indexing-samplesGet sample indexed URLs.

Get sample indexed URLs.

No input schema was published for this tool.

get-insearch-historyGet in-search (appearing in results) history.

Get in-search (appearing in results) history.

No input schema was published for this tool.

get-insearch-samplesGet sample URLs appearing in search.

Get sample URLs appearing in search.

No input schema was published for this tool.

get-search-events-historyGet search URL events history (appeared/removed).

Get search URL events history (appeared/removed).

No input schema was published for this tool.

get-search-events-samplesGet sample URLs for search events (appeared in / removed from search), with the reason each

Get sample URLs for search events (appeared in / removed from search), with the reason each

No input schema was published for this tool.

get-excluded-pagesPages DROPPED FROM SEARCH inside a time window, with the reason for each one (url +

Pages DROPPED FROM SEARCH inside a time window, with the reason for each one (url +

No input schema was published for this tool.

get-external-linksGet external links pointing to the site.

Get external links pointing to the site.

No input schema was published for this tool.

get-external-links-historyGet external links count history.

Get external links count history.

No input schema was published for this tool.

get-broken-internal-linksList broken internal links (destination URL, the source page linking to it, and when Yandex

List broken internal links (destination URL, the source page linking to it, and when Yandex

No input schema was published for this tool.

get-broken-internal-links-historyGet broken internal links count history.

Get broken internal links count history.

No input schema was published for this tool.

get-sitemapsList all sitemaps for a host.

List all sitemaps for a host.

No input schema was published for this tool.

get-sitemapGet details for a specific sitemap.

Get details for a specific sitemap.

No input schema was published for this tool.

get-user-sitemapsList user-added sitemaps.

List user-added sitemaps.

No input schema was published for this tool.

get-important-urlsGet important URLs for a site.

Get important URLs for a site.

No input schema was published for this tool.

get-important-url-historyGet history for a specific important URL.

Get history for a specific important URL.

No input schema was published for this tool.

get-recrawl-quotaGet recrawl quota for a host.

Get recrawl quota for a host.

No input schema was published for this tool.

get-recrawl-queueList recrawl queue for a host (URLs submitted via add-recrawl-url with their state).

List recrawl queue for a host (URLs submitted via add-recrawl-url with their state).

No input schema was published for this tool.

get-recrawl-taskGet state of a single recrawl task by task_id (returned by add-recrawl-url).

Get state of a single recrawl task by task_id (returned by add-recrawl-url).

No input schema was published for this tool.

verify-hostGet verification status and available verification methods for a host. Use after add-host to check what verification is needed.

Get verification status and available verification methods for a host. Use after add-host to check what verification is needed.

No input schema was published for this tool.

delete-hostprivilegedRemove a host (site) from Yandex Webmaster. IRREVERSIBLE: verification, indexing and search-query history,

Remove a host (site) from Yandex Webmaster. IRREVERSIBLE: verification, indexing and search-query history,

No input schema was published for this tool.

29 of 29 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Yandex Webmaster API — site analytics, indexing, search queries

Keywords
mcpmcp-servermodel-context-protocolclaudeclaude-codeyandexyandex-webmasterindexingsearch-consoleseo
Alternatives
Comparing tool surfaces…

Tools exposed

29 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-16 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in search & retrieval