Seyka.ru

ru.seykaPublished by seyka.ruOfficial publisherv1.0.0Updated Oct 30, 2026

Hosted SEO analytics and tools: Yandex, Google Search Console, Topvisor, Rush Analytics and Keys.so.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Hosted SEO analytics MCP server that lets an assistant pull search-performance and keyword data from Yandex, Google Search Console, Topvisor, Rush Analytics…

What you can do
  • Query SEO analytics data from connected sources such as Yandex, Google Search Console, Topvisor, Rush Analytics and Keys.so.
  • Retrieve search performance and keyword research information for analysis through the assistant.
  • No individual tools are documented, so the exact operations available are not specified.
When to use it
Useful when you want an assistant to consult SEO data — search performance, rankings or keyword research — from several Russian and international SEO platforms without building your own integrations.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime needed. Requires a bearer API key sent in the Authorization header, obtained from the provider's API keys page. Accounts with the underlying SEO services are presumably needed for their data.
Before you install
The API key is a credential sent in the Authorization header; keep it private and revoke it if exposed. The server reads data from third-party SEO platforms, so queries and results pass through the provider and those services. The manifest lists no tools, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Seyka.ru in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ru.seyka%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "seyka-ru": {
      "type": "http",
      "url": "https://mcp.seyka.ru/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Seyka integrations