Naver Yeti MCP MCP server

This MCP server provides a tool to validate whether an IP address is officially used by Naver Yeti for web crawling. It leverages the same continuously updated database as the Naver Yeti API, supporting both current and historic IP lookups to assist in log file analysis and SEO verification.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by SEOAPI

MCP endpoint (Streamable HTTP)

https://naverbot.seoapi.com/mcp

Vendor documentation

What you can do with it

Validate if an IP address is officially used by Naver Yeti
Analyze historical server logs for Naver crawler activity
Verify current Naver Yeti IP addresses for security

Tools advertised by the last live check:

validate_ip

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http naver-yeti-mcp https://naverbot.seoapi.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add naver-yeti-mcp --url https://naverbot.seoapi.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable naver-yeti-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "naver-yeti-mcp": {
      "url": "https://naverbot.seoapi.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "naver-yeti-mcp": {
      "type": "streamableHttp",
      "url": "https://naverbot.seoapi.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start naver-yeti-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "naver-yeti-mcp": {
      "type": "http",
      "url": "https://naverbot.seoapi.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http naver-yeti-mcp https://naverbot.seoapi.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "naver-yeti-mcp": {
      "url": "https://naverbot.seoapi.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "naver-yeti-mcp": {
      "serverUrl": "https://naverbot.seoapi.com/mcp"
    }
  }
}

See all 957

Do you run Naver Yeti MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing