Wet MCP vs Unblink

In-depth architectural comparison of the Wet MCP and Unblink 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.

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).
• You have access to required keys: WET_MCP_CONFIG.
• Primary tools included: search, extract, media.

Explore Wet MCP Details

Choose Unblink when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: read, browse, links.

Explore Unblink Details

Feature & Specification Comparison

Specification	Wet MCP n24q02m Search & Data Extraction	Unblink Search & Data Extraction
Summary	Web search (embedded SearXNG), content extraction, and library docs indexing with hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, no API keys required.	Pure-Go browser for AI: fetch pages, render JS without Chromium, return clean Markdown over MCP.
Category & Scope	Search & Data Extraction

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "n24q02m-wet-mcp": {
      "command": "uvx",
      "args": [
        "invocation"
      ],
      "env": {
        "WET_MCP_CONFIG": "YOUR_WET_MCP_CONFIG_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "unblink": {
      "url": "https://api.example.com"
    }
  }
}

Related MCP Server Comparisons