Open webSearch: MCP server, setup and security

What Open webSearch does

According to its repository: “Multi-engine web search across Bing, Baidu, DuckDuckGo, Brave, Exa and CSDN.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Open webSearch is listed under Web search and extraction, a category of 159 servers in the directory, where it ranks #8 by stars.

Installing and connecting Open webSearch

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Python, TypeScript.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Open webSearch. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on June 20, 2025, the Aas-ee/open-webSearch repository has 1,874 stars and 188 forks, with 11 open issues. It has more stars than 95% of the servers in the directory. It received changes this month.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.