In-depth architectural comparison of the Wet MCP and Scrapeless MCP Server 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
Wet MCP
Search & Data Extraction · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Scrapeless MCP Server
Search & Data Extraction · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Wet MCP if you need specialized Search & Data Extraction tools running via a local process. Choose Scrapeless MCP Server 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 Wet MCP 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 (embedded SearXNG), content extraction, and library docs indexing with hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, no API keys required.
The Scrapeless Model Context Protocol service acts as an MCP server connector to the Google SERP API, enabling web search within the MCP ecosystem without leaving it.
Category & Scope
Tools & Capabilities Breakdown
Wet MCP Tools (6)
search
Web (SearXNG metasearch), news, images, academic research (Scholar / arXiv / PubMed / CrossRef / Semantic Scholar / BASE), library docs (HyDE + FTS5), find similar pages. Includes `docs_resolve` (library name -> ranked id), `docs_query` (version-aware + topic + 5000-token cap), `docs_lock_project`…
extract
URL -> smart chunks dict (`clean_text` + `markdown` + `structured_data` + `code_blocks` + `metadata`) via web-core 5-strategy chain. Batch processing (up to 50 URLs), deep crawling, site mapping, local file conversion (PDF/DOCX/XLSX/PPTX/EPUB), structured extraction (JSON Schema)
media
list` (discover URLs from gallery pages), `download` (SSRF-safe). `analyze` was removed in v2.0.0 -- use `imagine-mcp.understand` instead
Wet MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Scrapeless MCP Server belongs to Search & Data Extraction using local stdio subprocess. Select Wet MCP when you need capabilities focused on search & data extraction and Scrapeless MCP Server 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.