// SCAN REPORT

Yandex Searchapi

7 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 30 Jun 2026

0 can modify or destroy data

7 read-only

7 tools total

Community server · catalogue entry verified 30/06/2026

How to control Yandex Searchapi ↓

TOOL MAP

What Yandex Searchapi exposes to your agents

Read (7) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Yandex Searchapi

PolicyLayer is an MCP gateway — it sits between your AI agents and Yandex Searchapi, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "generative_search": {
    "limits": [
      {
        "counter": "generative_search_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Yandex Searchapi — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON YANDEX SEARCHAPI →

Instant setup, no code required.

FULL CATALOGUE

All 7 Yandex Searchapi tools

READ 7 tools

Read generative_search Generate an answer grounded in web search results, with optional source restrictions (site/host/url). Read image_search Search images by text query. Returns grouped image documents and image metadata like thumbnail/original links. Read web_search Search web pages by text query. Returns grouped documents with URL, title, language, and snippet passages. Read wordstat_get_dynamics Get how search frequency changes over time for a keyword (daily, weekly, or monthly). Read wordstat_get_regions_distribution Get regional distribution for a keyword: where users search this phrase more often. Read wordstat_get_regions_tree Get the full tree of Wordstat region IDs and names. Useful for choosing region filters. Read wordstat_get_top Get popular and related search queries for a keyword using Yandex Wordstat.

FAQ

Questions about Yandex Searchapi

Is the Yandex Searchapi MCP server safe to use without restrictions? +

The Yandex Searchapi server is primarily read-only with 7 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Yandex Searchapi MCP server expose? +

7 tools across 1 categories: Read. 7 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Yandex Searchapi? +

Register the Yandex Searchapi MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Yandex Searchapi tool call.

Deterministic rules across all 7 Yandex Searchapi tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON YANDEX SEARCHAPI →

Instant setup, no code required.

7 Yandex Searchapi tools catalogued and risk-classified — across an index of 43,000+ MCP servers.