MCP Zoomeye vs Fetch

In-depth architectural comparison of the MCP Zoomeye and Fetch 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 MCP Zoomeye when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: ZOOMEYE_API_KEY.
• Primary tools included: zoomeye_search.

Explore MCP Zoomeye Details

Choose Fetch 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).
• Primary tools included: create_entities, create_relations, add_observations.

Explore Fetch Details

Feature & Specification Comparison

Specification	MCP Zoomeye zoomeye-ai Search & Data Extraction	Fetch VerifiedSearch & Data Extraction
Summary	Querying network asset information by ZoomEye MCP Server	Web content fetching and conversion for efficient LLM usage.
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": {
    "zoomeye-ai-mcp-zoomeye": {
      "command": "uvx",
      "args": [
        "installation"
      ],
      "env": {
        "ZOOMEYE_API_KEY": "YOUR_ZOOMEYE_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

Related MCP Server Comparisons