SkillFoxx

SerpentSeek search gateway with 39 providers MCP

SerpentSeek

A self-hosted Go search gateway with an MCP search tool: 39 providers, including the official Yandex Search API v2

  • 2 ★ on the repository
  • Last commit
  • GPL-3.0
MCP server

Extended access

Why this level

  • Requests run under the paid keys of whoever deployed the service, and the cost falls on them
  • The admin panel exposes provider keys and the history of every request
All reasons and checks
Russian stack

liberide/serpent-seekAuthor:liberide

Install

Manual install

cp .env.example .env && docker compose up --build

Quick start from the README; the UI comes up at localhost:8080, providers are configured after logging into the admin panel.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Requests run under the paid keys of whoever deployed the service, and the cost falls on them
  • The admin panel exposes provider keys and the history of every request

This is third-party code. Review the repository files before installing.

What it does

SerpentSeek is a unified gateway for 39 built-in search providers: SearXNG, Brave, Google Vertex AI Search, Yandex, SerpApi, DataForSEO, Exa, Tavily, Kagi, Perplexity and more, with a visual fallback-chain editor between providers. Yandex is wired in as the yandex driver with an api_key and folder_id against the official /v2/web/search endpoint, and the YandexGPT generative answer is available as a separate yandex_gen driver via /v2/gen/search on an answer-type node. The server exposes a single MCP search tool over streamable HTTP with Bearer-token auth, supports an stdio wrapper via mcp-remote for clients without HTTP transport, keeps request history with live SSE tracing, and stores data in SQLite or PostgreSQL. All requests run under the keys of whoever deployed the service and are billed to them.

Who it is for. For teams that want one self-hosted search gateway with fallback between providers, including official Yandex search, serving both Open WebUI and MCP clients.

Good fit when

  • You need fallback between several search providers, including Yandex, in one chain
  • You need both a /search endpoint for Open WebUI and an MCP tool for Claude, Cursor, VS Code at once
  • Request auditing, API keys and WebAuthn passkeys for the admin panel matter to you

Not a fit when

  • You only need Yandex without the other 38 providers: a dedicated Yandex Search API MCP server is simpler
  • You do not want to deploy and administer a separate service: SerpentSeek is a full application with a database and web panel

Example request

Search Yandex for recent material on the new law and give a short generated answer with links

MCP

Transport
http
Authentication
key is optional

Environment variables

GOOGLE_API_KEY secret
Key for the default google_vertex provider seeded on first start
SEARXNG_URL
URL of an external SearXNG instance, if that provider is used

Limitations

The Yandex Search API is paid; an api_key and Yandex Cloud folder_id must be configured on the Providers page after first start. Passkeys require HTTPS and a domain; over HTTP or a bare IP only API keys are available. SearXNG is not bundled and must be deployed separately under AGPLv3. All provider costs are billed to whoever deployed the service; the project authors are not liable for them.

How to disable. Run docker compose down and remove the serpentseek MCP server from your client.

FAQ

Can several providers be used with fallback?

Yes, the visual chain editor lets you order providers, including several instances of the same driver with different keys.

Does Yandex's generative answer need a separate key?

Yes, the yandex_gen driver uses its own api_key and folder_id on an answer-type node.

Discussion

No questions or reviews yet.

All Yandex Search tools
Russian stack

An MCP server for the OpenSERP search platform: web and image search across several engines including Yandex, plus page text extraction

MCP serverExtended access3
Russian stack

An MCP web-search and content-extraction server via Yandex and Google on top of SerpAPI, geared toward RU/CIS results

MCP serverExtended access1
Russian stack

A self-hosted MCP for Yandex Search API v2: web, image and generative search across all six Yandex indexes

MCP serverExtended access4
Russian stack

A search MCP server on the Yandex Cloud Search API with a monitoring dashboard, Brave fallback and an offline bundle for air-gapped networks

MCP serverExtended access

Yandex Search API v2 MCP server over HTTP

Yandex Search API MCP server, StreamableHTTP build

Russian stack

A fork of Yandex's official server adding HTTP transport and the full range of search types: web, generative, image

MCP serverExtended access1

Yandex Search API MCP with deferred search

Yandex Search MCP Server (Async Mode)

Russian stack

A fork of Yandex's official server defaulting to deferred async search, cutting Search API cost by up to 94%

MCP serverExtended access

README in short

The README lists all 39 providers by category (web/SERP, AI search, academic, enterprise, generative answer nodes) with their credential fields, shows a docker compose quick start, Open WebUI and MCP integration, PostgreSQL setup, API-key and passkey authentication, background cleanup jobs, and a risks section about paid providers and who bears the cost.

README badge

Report a problem