In-depth architectural comparison of the Open WebSearch and Wet MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Open WebSearch
Search & Data Extraction · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Wet MCP
Search & Data Extraction · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Open WebSearch if you need specialized Search & Data Extraction tools running via a local process. Choose Wet MCP if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Open WebSearch when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Web search using free multi-engine search (NO API KEYS REQUIRED) — Supports Bing, Baidu, DuckDuckGo, Brave, Exa, and CSDN.
Web search (embedded SearXNG), content extraction, and library docs indexing with hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, no API keys required.
Search the web using multiple engines (e.g., Baidu, Bing, DuckDuckGo, CSDN, Exa, Brave, Juejin(掘金), Startpage, Sogou(搜狗)) with no API key required. searchMode meanings: omit or set auto to use the server configured SEARCH_MODE; request forces request-based search; playwright forces browser-based search.
fetchLinuxDoArticle
Fetch full article content from a linux.do post URL
fetchCsdnArticle
Fetch full article content from a csdn post URL
fetchGithubReadme
Fetch README content from a GitHub repository URL
fetchWebContent
Fetch content from a public HTTP(S) URL (supports Markdown files and normal web pages)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Open WebSearch is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Wet MCP belongs to Search & Data Extraction using local stdio subprocess. Select Open WebSearch when you need capabilities focused on search & data extraction and Wet MCP when you require tools for search & data extraction.
Re-trigger the zero-config relay setup flow (prints a fresh relay URL for the browser form). Registered via `mcp-core`'s `register_open_relay_tool` so an LLM can restart setup without a manual restart.