Developer · Local MCP server
SEO Tools: Yandex Wordstat
MCP server for Yandex Wordstat keyword frequencies (official API v2). Free Yandex Cloud Search API.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.antohins/seo-tools-mcp-wordstat- Version
- 1.8.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-25
- Updated
- 2026-08-25
- Publisher
- antohins (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/antohins) · how
- Website
- github.com/antohins/seo-tools-mcp#readme
- Repository
- github.com/antohins/seo-tools-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | seo-tools-mcp-wordstat | 1.8.0 | stdio |
How to connect SEO Tools: Yandex Wordstat
SEO Tools: Yandex Wordstat runs locally from a Node.js package published to the npm registry: seo-tools-mcp-wordstat version 1.8.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y seo-tools-mcp-wordstat@1.8.0. It reads these environment variables: WORDSTAT_API_KEY (secret) and WORDSTAT_FOLDER_ID; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"seo-tools-mcp-wordstat": {
"command": "npx",
"args": [
"-y",
"seo-tools-mcp-wordstat@1.8.0"
],
"env": {
"WORDSTAT_API_KEY": "<secret>",
"WORDSTAT_FOLDER_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from antohins (GitHub)
| Server | Runs |
|---|---|
| SEO Tools: A-Parser bridgeBridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only). | Local · stdio |
| SEO Tools: Google Analytics 4Google Analytics 4: reports, traffic sources, landing pages, events, realtime (read-only). | Local · stdio |
| SEO Tools: Google Search ConsoleGoogle Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct). | Local · stdio |
| SEO Tools: XMLRiver SERP (Google + Yandex)Google & Yandex SERP, image/news verticals and URL indexation checks via XMLRiver (read-only). | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| SentrikGovernance runtime for AI-generated code. Enforce compliance and security standards. | Local · stdio |
| Sentry MCPMCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants. | Remote & Local · HTTP, stdioLive check: sign-in required |
| SentrydockDelegate standing watches over companies and topics. Get signed webhook alerts. OAuth/API. | Remote · HTTPLive check: sign-in required |
| SenzingEntity resolution - data mapping, SDK code generation, docs search, and error troubleshooting. | Remote · HTTPLive check: ✓ handshake |
| Seo Web Analysis MCP ServerRun Lighthouse audits, check SSL certificates, detect tech stacks, query WHOIS and DNS records. | Local · stdio |
| SeracadeLLM cost optimization. Audit your calls, prove savings, route to the cheapest quality model. BYOK. | Local · stdio |
| Serena MCP: the IDE for your agentA toolkit for coding, providing semantic retrieval and editing capabilities. | Local · stdio |
| Serial MCPMCP server for serial port communication. 25 tools, resources, prompts, and stdio/HTTP transports. | Local · stdio |