Kagimcp vs Not Human Search

In-depth architectural comparison of the Kagimcp and Not Human Search 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 Kagimcp 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: KAGI_API_KEY.
• Primary tools included: kagi_search_fetch, kagi_extract.

Explore Kagimcp Details

Choose Not Human Search 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: search_agents, get_site_details, get_stats.

Explore Not Human Search Details

Feature & Specification Comparison

Specification	Kagimcp kagisearch VerifiedSearch & Data Extraction	Not Human Search Search & Data Extraction
Summary	The Official Model Context Protocol (MCP) server for Kagi Search & other tools.	Search the agentic web. 960+ sites scored 0-100 on agentic readiness. Includes verify_mcp tool.
Category & Scope

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": {
    "kagisearch-kagimcp": {
      "command": "uvx",
      "args": [
        "kagimcp"
      ],
      "env": {
        "KAGI_API_KEY": "YOUR_KAGI_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "not-human-search-2": {
      "url": "https://nothumansearch.ai/mcp"
    }
  }
}

Related MCP Server Comparisons