open-webSearch MCP
open-websearch
Web search with no API keys: an MCP server, a CLI and a local daemon. It works by parsing search engine pages so it may break
- 1,853 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- Search engine page parsing may break
- Falls under search engine terms
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/open-websearchDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Search engine page parsing may break
- Falls under search engine terms
This is third-party code. Review the repository files before installing.
What it does
open-webSearch searches the web with no API keys: it is an MCP server, a CLI and a local daemon in one package. Launch: `npx open-websearch@latest`, permanent installation `npm install -g open-websearch`, and the stdio mode and default search engine are set by the `MODE` and `DEFAULT_SEARCH_ENGINE` variables. The skill installs with `npx skills add https://github.com/Aas-ee/open-webSearch --skill open-websearch`. Version 2.2.0 from 28.09.2026, Apache-2.0 license. Search works by parsing search engine pages.
Who it is for. For people who need web search for an agent with no sign-up and no paid API keys.
Good fit when
- You need web search for an agent with no API keys
- You need an MCP server, a CLI and a daemon in one package
- You need a choice of search engine through variables
Not a fit when
- You need stable operation: page parsing may break
- Search engine terms forbid automatic parsing
Example request
Find three fresh reviews of the new library version and give links to the sourcesMCP
- Transport
- stdio, http
- Authentication
- not required
Limitations
Search works by parsing search engine pages, so it may break when their markup changes and falls under their terms of use. The README has an advertising block of a proxy service sponsor that is not part of the package work. Access is minimal: network requests, with no file changes.
How to disable. Remove the server entry from the client and the package with npm uninstall -g open-websearch.
FAQ
Are API keys needed?
No, search works with no keys by parsing search engine pages.
How do I launch it?
npx open-websearch@latest.
Why may it break?
Because it relies on search engine page markup, which changes.
Discussion
No questions or reviews yet.
Related
MCP serversA unified search MCP server: one interface to Tavily, Brave, Kagi, Exa, Linkup, Firecrawl and GitHub search
MCP server for real-time web search: general and vertical search, batch queries and page content extraction
OpenSERP MCP server with Yandex search
@openserp/mcp
An MCP server for the OpenSERP search platform: web and image search across several engines including Yandex, plus page text extraction
An MCP server for private web search through your SearXNG instance: search with pagination and filters, page and PDF reading
Yandex search MCP server with offline install
MCP Search Server
A search MCP server on the Yandex Cloud Search API with a monitoring dashboard, Brave fallback and an offline bundle for air-gapped networks
Web search via DuckDuckGo and page reading for the agent with no API keys, with built-in rate limiting
README in short
The README describes search with no API keys: an MCP server, a CLI and a daemon, launch through npx and a skill. Apache-2.0 license.