one-search-mcp and wet-mcp
These two tools are competitors, as both are MCP (Multi-Content Platform) servers designed to provide web search, content extraction, and similar functionalities, offering alternative implementations for the same core purpose.
About one-search-mcp
yokingma/one-search-mcp
🚀 OneSearch MCP Server: Web Search & Scraper & Extract, Support agent-browser, SearXNG, Tavily, DuckDuckGo, Bing, etc.
Implements Model Context Protocol (MCP) server with pluggable search backends (SearXNG, Tavily, DuckDuckGo, Bing, Google, etc.) and exposes four tools—`one_search`, `one_scrape`, `one_map`, `one_extract`—for web search, scraping, and structured data extraction. Uses local browser automation via `agent-browser` for privacy-preserving searches and scraping without external API dependencies, with automatic Chromium detection across Chrome, Edge, and Canary installations. Integrates with Claude Desktop, Cursor, and Windsurf through standard MCP configuration files.
About wet-mcp
n24q02m/wet-mcp
MCP server for web search, content extraction, and documentation indexing
Provides embedded metasearch (SearXNG) with semantic reranking and query expansion, plus specialized academic research across Google Scholar, arXiv, and PubMed. Features local full-text documentation indexing with HyDE-enhanced retrieval, batch content extraction from up to 50 URLs, and multimodal analysis—all with zero-config local embeddings (Qwen3) or optional cloud providers. Integrates as an MCP server with Claude, Gemini, and Codex via stdio transport, with automatic setup and encrypted credential storage.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work