Iskat — Russian-language web search for agents MCP Server
by
iskat
Your server? Claim it
not responding
Iskat — Russian-language web search for agents is listed as active in the registry but did not answer our last check. It exposes 14 tools.
Russian-language web search for agents: hybrid retrieval, product prices, full page text
Uptime history
72 days of history · worst day 0%
72 days agonow
0.0%
Uptime 24h
0 of 92 checks
14
Tools
read from the server
62 ms
Response time
average over 24h
open, no key
Access
streamable-http
Iskat — Russian-language web search for agents does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
run in your terminal
claude mcp add webdex --transport http https://iskat.io/mcpSettings → Connectors → Add custom connector, then paste this address
https://iskat.io/mcp~/.codex/config.toml
[mcp_servers.webdex]
url = "https://iskat.io/mcp".cursor/mcp.json
{
"mcpServers": {
"webdex": {
"url": "https://iskat.io/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"webdex": {
"type": "http",
"url": "https://iskat.io/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
watch
check_watch
Return pages matching a watched query that were indexed since the last check, then advance the cursor. Call with no id to check all of your watches at once.
delete_watch
Remove a watch. Pass its id (from list_watches) or the exact query text. Watches accumulated with no way to remove them; this closes that.
watch_query
Save a query and later ask what has appeared since you last checked. Pull-based: nothing is pushed to you, you call check_watch when you want to know — which fits an agent that runs on its own schedule.
Use for monitoring: a topic, a competitor, a regulation, a product.
batch
search_batch
Execute up to 10 queries in one call. Answering a real question usually takes several related searches, and doing them one at a time spends a round trip on each; this runs them together and returns the results grouped by query.
index
index_stats
Size and freshness of the corpus: sites, pages, passages, languages.
page
fetch_page
Return the full extracted text of a page already in the index. This serves stored content and does not hit the live site, so it is fast and cannot be blocked. Use it after search to read a result.
pages
fetch_pages
Like fetch_page but for up to 20 URLs in one call — the bulk-read counterpart to search_batch, so reading a page of results is one round trip instead of ten. Each page comes back with its cleaned text from the index; URLs not in the index are marked, not fatal.
passages
find_passages
Return the specific passages that answer a question, each with the URL and title it came from. Use this when you intend to cite or summarise rather than browse: it skips the step of fetching pages and hunting for the relevant paragraph, and the attribution is exact.
products
search_products
Search shop catalogues by name and specification, filter by price and availability, and sort by price. Use this rather than `search` whenever the question is what something costs or where to buy it: `search` returns pages that mention a product, this returns the offer itself — price, stock, specifications and a link straight to the product page. Specifications are searchable, so a query like "ноутбук 16 гб 512 ссд" or "холодильник samsung no frost" matches on capacity and features, not just the model name. Coverage is whatever has been crawled: an exact model, colour and size that no indexed shop stocks returns nothing rather than the wrong colour — an empty result means not indexed, not nonexistent.
search
search
Search the Webdex index of crawled websites. Combines keyword (BM25) and semantic (vector) retrieval. Supports "quoted phrases" for exact matches and -term to exclude a term. Works across languages: a query in one language can retrieve pages written in another.
similar
find_similar
Given an indexed URL, return other indexed pages with similar content, compared by meaning rather than shared keywords.
sites
list_sites
Show which sites the index covers, with page counts. Use this to understand coverage before concluding that something is missing.
source
source_profile
Describe a site in the index: what type of source it is (official, media, reference, forum, shop), how much of it we hold, how trusted it is by the link graph, and how fresh the copy is.
Use this before relying on a result. A ministry's own page and a forum post repeating it are both 'a URL', and the difference decides how much weight the claim deserves.
watches
list_watches
Show the queries you are watching and when each was last checked.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://iskat.io/mcp | streamable-http | answering | 62 ms | 2 min ago |
Alternatives to Iskat — Russian-language web search for agents
same job, measured the same wayIskalo — Russian Web Search
by iskalo
Search the Russian web with contact, city and provider filters; retrieve indexed page contents.
S
search-mcp
by ioconnex
Web search and clean-text page fetch for AI agents, with SSRF protection.
Trawlia
by trawlia
Web search and page extraction for agents, returned as readable text rather than raw JSON.
Web Search (Tanod)
by tanod
Search the web and the news from an agent, with page text in the results when you ask for it.
web-retrieval-mcp
by velvetsp
MCP web search + tiered web fetch for AI agents (Exa, Firecrawl), SSRF-guarded, cross-platform.
call402 — x402 Agent Services
by lgs1520
x402 pay-per-call APIs for agents: web search, wallet/token checks, text structuring.
SingIt x402
by singitai
Web search, page reading, prices and market data for agents, billed to your SingIt API key in USDC.
Deep Research MCP Server
by perufitlife
Web search, clean page reading & one-call research dossiers for AI agents. No API key.
Iskat — Russian-language web search for agents — questions
Answers built from our own checks of this server.
What can Iskat — Russian-language web search for agents do?
It exposes 14 tools, read directly from the server on our last check. Among them: check_watch, delete_watch, fetch_page, fetch_pages, find_passages, find_similar and 8 more. 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 Iskat — Russian-language web search for agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 62 ms. The bar chart above shows every period we have measured.
The registry lists Iskat — Russian-language web search for agents as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Iskat — Russian-language web search for agents?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Iskat — Russian-language web search for agents need an API key?
No. Iskat — Russian-language web search for agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.