Naverbot

com.seoapiPublished by seoapi.comOfficial publisherv1.0.0Updated Oct 24, 2026

Validate Naver Yeti IP addresses. Remote MCP validate_ip tool.

The publisher's own server: Amazon

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant validate Naver Yeti crawler IP addresses.

What you can do
This server exposes a single remote tool, validate_ip, for checking whether an IP address belongs to Naver's Yeti crawler. The assistant sends an address and receives a validation result. It runs entirely as a hosted endpoint, so no local tooling is involved.
When to use it
Useful when you need to confirm that traffic claiming to come from Naver's Yeti search crawler is genuine, for example when reviewing server logs or filtering bot requests. It is a narrow, single-purpose check rather than a general search or SEO suite.
Requirements
A remote MCP client that can connect to the streamable HTTP endpoint. No packages, environment variables, headers, or accounts are declared.
Before you install
The service is hosted by a third party, so the IP addresses you submit are sent to that provider. No authentication is declared, so treat the endpoint as public and avoid sending sensitive data beyond the addresses being checked.

Installation

In SourceWeft

  1. Open Naverbot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.seoapi%2Fnaverbot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "naverbot": {
      "type": "http",
      "url": "https://naverbot.seoapi.com/mcp"
    }
  }
}

Tools

1

validate_ip

Validate Naver Yeti IP

Check whether an IP address (IPv4 or IPv6) is a genuine Naver Yeti IP address, verified against Naver Yeti's published IP data on seoapi.com.

Parametersiprequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Seoapi integrations