Yandex Wiki Search Mcp

io.github.dlbolshovPublished by GitHub account dlbolshovv1.6.0Updated Oct 24, 2026

MCP server for Yandex Wiki with full-text search.

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Lets an assistant run full-text searches against Yandex Wiki content from a local MCP server.

What you can do
This MCP server exposes Yandex Wiki full-text search to an AI assistant. The registry description states only that it provides full-text search over Yandex Wiki; no individual tools are listed in the manifest. It runs as a local stdio process rather than a remote endpoint.
When to use it
Useful when an assistant needs to look up pages or documents stored in Yandex Wiki during a conversation, for example to answer questions from internal documentation. It is not intended for general web search or for wikis other than Yandex Wiki.
Requirements
Runs locally as a stdio process, distributed as a PyPI package (yandex-wiki-search-mcp) or an OCI image. The manifest declares no authentication, environment variables, or headers, so any credentials or endpoint configuration needed to reach a Yandex Wiki instance are not documented here. Desktop only.
Before you install
The registry description gives no details about credentials, write operations, or data handling. Because it queries a Yandex Wiki instance, search terms and results may pass through Yandex services; review the provider's documentation before use.

Installation

In SourceWeft

  1. Open Yandex Wiki Search Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v1.6.0LatestOct 12, 2026
  2. v1.5.2Oct 12, 2026
  3. v1.5.1Sep 23, 2026
  4. v1.5.0Sep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.