Naver Search MCP vs Stocky — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Naver Search MCP vs Stocky
In-depth architectural comparison of the Naver Search MCP and Stocky 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
Naver Search MCP
Search & Data Extraction · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Stocky
Search & Data Extraction · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Naver Search MCP if you need specialized Search & Data Extraction tools running via a local process. Choose Stocky 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 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)).
You have access to required keys: NCP_APIGW_API_KEY_ID, NCP_APIGW_API_KEY, NAVER_CLIENT_ID, NAVER_CLIENT_SECRET.
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.
Category search tool so you no longer need to manually check category numbers in URLs for trend and shopping insight searches. Just describe the category in natural language.
search_webkr
Search Naver web documents
search_news
Search Naver news
search_blog
Search Naver blogs
search_cafearticle
Search Naver cafe articles
search_image
Search Naver images
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).
Naver Search MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Stocky belongs to Search & Data Extraction using local stdio subprocess. Select Naver Search MCP when you need capabilities focused on search & data extraction and Stocky when you require tools for search & data extraction.
MCP server for Naver Search API integration, supporting blog, news, shopping search and DataLab analytics features.
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.