What is the key difference between Stocky and Naver Search MCP?

Stocky belongs to the Search & Data Extraction category with local stdio execution, while Naver Search MCP belongs to the Search & Data Extraction category with local stdio execution.

How do I install Stocky or Naver Search MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Stocky and Naver Search MCP free or paid?

Stocky operates under a BYOK (Pay Provider Direct) model (API Key required). Naver Search MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Stocky lists 6 tools with 1 views and 27 GitHub stars. Naver Search MCP lists 18 tools with 3 views and 85 GitHub stars.

Can I use both Stocky and Naver Search MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Stocky vs Naver Search MCP

In-depth architectural comparison of the Stocky and Naver Search MCP 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

Stocky

Search & Data Extraction · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Naver Search MCP

Search & Data Extraction · Local stdio

Quality: 64/100 (Good) | Auth: API Key required

Verdict Summary: Choose Stocky if you need specialized Search & Data Extraction tools running via a local process. Choose Naver Search MCP 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 Stocky 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: PEXELS_API_KEY, UNSPLASH_ACCESS_KEY, ENABLE_ATTRIBUTION_LINKS, STOCKY_CACHE_TTL, STOCKY_HTTP_TIMEOUT, STOCKY_MAX_DOWNLOAD_BYTES, STOCKY_DOWNLOAD_ROOT, STOCKY_LOG_LEVEL.
Primary tools included: Concurrent multi-provider search (Pexels and Unsplash), Rich metadata including image sizes, photographer, tags, License-aware attribution generation per provider requirements.

Explore Stocky Details

Choose Naver Search MCP 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)).

Feature & Specification Comparison

Specification	Stocky joelio Search & Data Extraction	Naver Search MCP isnow890 Search & Data Extraction
Summary	An MCP server for searching and downloading royalty-free stock photography from Pexels and Unsplash. Features multi-provider search, rich metadata, pagination support, and async performance for AI assistants to find and access high-quality images.	MCP server for Naver Search API integration, supporting blog, news, shopping search and DataLab analytics features.
Category & Scope

Tools & Capabilities Breakdown

Stocky Tools (6)

Concurrent multi-provider search (Pexels and Unsplash)

Rich metadata including image sizes, photographer, tags

License-aware attribution generation per provider requirements

Search result caching with configurable TTL

Filters for orientation, color, and sorting (provider-specific)

Error reporting for failing providers instead of silent empty results

Naver Search MCP Tools (18)

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

Stocky Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "joelio-stocky": {
      "command": "uvx",
      "args": [
        "stocky-mcp"
      ],
      "env": {
        "PEXELS_API_KEY": "YOUR_PEXELS_API_KEY_HERE",
        "UNSPLASH_ACCESS_KEY": "YOUR_UNSPLASH_ACCESS_KEY_HERE",
        "ENABLE_ATTRIBUTION_LINKS": "YOUR_ENABLE_ATTRIBUTION_LINKS_HERE",
        "STOCKY_CACHE_TTL": "YOUR_STOCKY_CACHE_TTL_HERE",
        "STOCKY_HTTP_TIMEOUT": "YOUR_STOCKY_HTTP_TIMEOUT_HERE",
        "STOCKY_MAX_DOWNLOAD_BYTES": "YOUR_STOCKY_MAX_DOWNLOAD_BYTES_HERE",
        "STOCKY_DOWNLOAD_ROOT": "YOUR_STOCKY_DOWNLOAD_ROOT_HERE",
        "STOCKY_LOG_LEVEL": "YOUR_STOCKY_LOG_LEVEL_HERE"
      }
    }
  }
}

Naver Search MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "isnow890-naver-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@isnow890/naver-search-mcp"
      ],
      "env": {
        "NCP_APIGW_API_KEY_ID": "YOUR_NCP_APIGW_API_KEY_ID_HERE",
        "NCP_APIGW_API_KEY": "YOUR_NCP_APIGW_API_KEY_HERE",
        "NAVER_CLIENT_ID": "YOUR_NAVER_CLIENT_ID_HERE",
        "NAVER_CLIENT_SECRET": "YOUR_NAVER_CLIENT_SECRET_HERE"
      }
    }
  }
}

Frequently Asked Questions

Stocky is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Naver Search MCP belongs to Search & Data Extraction using local stdio subprocess. Select Stocky when you need capabilities focused on search & data extraction and Naver Search MCP when you require tools for search & data extraction.

More alternatives to Stocky More alternatives to Naver Search MCP Search & Data Extraction category hub Canonical compare URL