Yandex and Google search MCP server
web-compass
An MCP web-search and content-extraction server via Yandex and Google on top of SerpAPI, geared toward RU/CIS results
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- It only runs search queries and extracts text from public pages, with no authorization and no writes
Install
Manual install
npm run build && npm run start:prodBuild and run the production server; SERPAPI_KEY is needed in .env.
This is third-party code. Review the repository files before installing.
What it does
The server offers five MCP tools, each with a matching REST endpoint: search_yandex searches via Yandex with a Russia or CIS region, search_google searches globally via Google, extract pulls the main readable text from a list of URLs, and search_and_extract_yandex and search_and_extract_google combine search and extraction in one call. Search runs through the third-party SerpAPI service, which returns Yandex and Google results without directly scraping their pages, and content extraction uses the Mozilla Readability engine, the same one behind Firefox Reader Mode. The server runs over streamable-http and connects by URL rather than launching as a local agent process.
Who it is for. For agents that need web search focused on Russian and CIS results alongside global Google search.
Good fit when
- You need Yandex search with a Russia or CIS region choice
- You want search and readable-text extraction combined in one call
- You are fine relying on the paid third-party SerpAPI service instead of direct scraping
Not a fit when
- You do not want to pay for a SerpAPI key: search does not work without one
- You need a local stdio server rather than a streamable-http URL connection
Example request
Search Yandex for the latest central bank rate news and extract the text of the top three articlesLimitations
You need a paid SERPAPI_KEY from the third-party SerpAPI service; without it no search tool works. No license is stated. You need to deploy and keep the server running yourself, there is no ready-made public endpoint.
How to disable. Remove the web-compass entry from your MCP client configuration and stop the server process.
MCP
- Transport
- http
- Authentication
- not required
| Environment variables | |
|---|---|
| SERPAPI_KEY required, secret | A paid third-party SerpAPI key for Yandex and Google search |
Security check
- It only runs search queries and extracts text from public pages, with no authorization and no writes
README in short
The README explains why RU/CIS via Yandex sits alongside Google, describes the five tools with parameters and their matching REST endpoints, a Claude Desktop config example over streamable-http, how it is built on SerpAPI and Mozilla Readability, and the dev and production run commands.
FAQ
Does the server scrape Yandex results directly?
No, results come through the third-party SerpAPI service, which itself fetches Yandex and Google data.
Do I need a key to use it?
Yes, without a paid SERPAPI_KEY neither Yandex nor Google search works.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills