MCP server and REST API giving AI agents live access to the web — with especially deep coverage of Russian-language sources. **Eight tools in one server:** - **web_search** — Live web search across multiple engines. Returns ranked results with title, URL and snippet. Supports time filters (day/week/month/year), language selection (auto/ru/en), category (general/news/it/science), domain allow/block lists, and an `excerpts` flag that pulls full page text for the top results in one call. - **image_search** — Image search returning direct file URLs, source pages and resolution. Up to 48 results per call. - **read_url** — Fetches a single page and returns clean Markdown — no ads, no navigation, no HTML. JavaScript is executed server-side so SPAs and React apps read correctly. Long pages are paginated via `offset`. - **read_urls** — Same as read_url but reads up to 5 URLs in parallel in one call. Failed URLs are listed separately; the rest still return. - **fetch_page** — Opens a page in a real browser (Chromium), returns a screenshot image plus page Markdown. Use when you need to see layout, colours or visual design rather than just text. - **extract** — Reads a page and returns only the fields you request via a JSON schema. Nothing else reaches your context. Up to 5 URLs per call with one schema applied to all. - **deep_research** — Multi-step agentic research: searches the web, reads sources, synthesises a coherent answer with citations. Takes 10 seconds to 2 minutes. Use for complex analytical questions, not quick facts. - **get_usage** — Returns current balance, daily quota used, and per-tool credit prices. Free to call, does not consume quota. **Why srezai for Russian-web tasks:** Proxy infrastructure is routed through Russia, so Yandex, Mail.ru, VK, Habr, and other Russia-first services return real results instead of being blocked or rate-limited. **Output is LLM-ready:** all tools return clean Markdown or JSON — no HTML parsing on your side, fewer input tokens per call. **Authentication:** static Bearer key issued at https://srezai.ru/dashboard. Credit top-up via the same dashboard.

MCP readiness

B · 76/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	22/25	Endpoint answers the MCP initialize handshake (9606 ms); near timeout response -3.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	11/15	22/30 probes succeeded over 30 days (73%).
Tool declaration	10/10	Lists 12 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Near timeout (9606 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 36% of peers; This listing 76 · peer median 81
Latency: Faster than 5% of peers; This listing 1,612 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
Uptime (30 days) −4 — Stay reachable in our daily probes.
Now: 22/30 probes succeeded over 30 days (73%).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-09-07 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/srezai/srezai-search/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/srezai/srezai-search/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://srezai.ru

Listed at (smithery)

https://srezai.ru