mcpbeat

Yandexbot MCP Server

com.seoapi/yandexbot
answering

Yandexbot is answering right now. Last checked moments ago. It exposes 1 tools.

Validate whether an IP address belongs to YandexBot. Remote MCP server exposing a validate_ip tool.

Uptime history 44 hours of history · worst hour 25%
44 hours agonow
96.7%
Uptime 24h
89 of 92 checks
1
Tools
read from the server
54 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add yandexbot --transport http https://yandexbot.seoapi.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "yandexbot": {
      "url": "https://yandexbot.seoapi.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.yandexbot]
url = "https://yandexbot.seoapi.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "yandexbot": {
      "url": "https://yandexbot.seoapi.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "yandexbot": {
      "url": "https://yandexbot.seoapi.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://yandexbot.seoapi.com/mcp streamable-http answering 82 ms 0 min ago

Yandexbot — questions

Answers built from our own checks of this server.

What can Yandexbot do?
It exposes 1 tools, read directly from the server on our last check. Among them: validate_ip. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Yandexbot working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 92 checks got a reply (96.7%), average response time 54 ms. The bar chart above shows every period we have measured.
How do I connect Yandexbot?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Yandexbot need an API key?
No. Yandexbot completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Yandexbot?
It answers our handshake in 54 ms on average, which is faster than 97% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.