Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Iskat — Russian-language web search for agents

REMOTE · ISKAT.IO

Russian-language web search for agents: hybrid retrieval, product prices, full page text

Available components

0 this week 25 Trust /100

Last scanned (13 hours ago)

Scores higher than 9% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 25
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.60 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 3 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Sept 26 0
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 65 functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 0 functional
  • 28 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Oct 2026 · Probed https://iskat.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.iskat.io CN=YE1,O=Let's Encrypt,C=US 9 Aug 2026 7 Nov 2026 ECDSA 256 ECDSA-SHA384 61f38723c5257a17c3430b845696bc394d7
SANs: iskat.io, www.iskat.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of iskat.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690, 57355 8, 8 Verified
iskat.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 502
Header Value
strict-transport-security max-age=15552000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://iskat.io/mcp HTTP error 502
http (plaintext) http://iskat.io/mcp HTTPS enforced 301 https://iskat.io/mcp
MCP tools · 14 exposed · ~1,414 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_watch ~61

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.

NameTypeReqDescription
idinteger–Watch id; omit to check all.
limitinteger––

No output schema declared.

No examples provided.

delete_watch ~69

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.

NameTypeReqDescription
idinteger–Watch id from list_watches.
querystring–Exact watched query, as an alternative to id.

No output schema declared.

No examples provided.

fetch_page ~79

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.

NameTypeReqDescription
maxCharsinteger–Truncate the body to this many characters.
urlstringyesURL of an indexed page.

No output schema declared.

No examples provided.

fetch_pages ~94

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.

NameTypeReqDescription
maxCharsinteger–Truncate each body to this many characters.
urlsarrayyesURLs of indexed pages.

No output schema declared.

No examples provided.

find_passages ~86

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.

NameTypeReqDescription
categorystring––
limitinteger–Number of passages.
querystringyes–

No output schema declared.

No examples provided.

find_similar ~49

Given an indexed URL, return other indexed pages with similar content, compared by meaning rather than shared keywords.

NameTypeReqDescription
limitinteger––
urlstringyesURL of an indexed page.

No output schema declared.

No examples provided.

index_stats ~23

Size and freshness of the corpus: sites, pages, passages, languages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sites ~58

Show which sites the index covers, with page counts. Use this to understand coverage before concluding that something is missing.

NameTypeReqDescription
limitinteger––
searchstring–Filter by substring of the host.
statusstring––

No output schema declared.

No examples provided.

list_watches ~22

Show the queries you are watching and when each was last checked.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~291

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.

NameTypeReqDescription
categorystring–Restrict to a task category, e.g. "news", "legal", "forum-it". See list_sites.
expandboolean–Widen the query with synonyms and acronym expansions (грм → газораспределительный механизм, НДФЛ → налог на доходы). On by default; set false for an exact-terms search. The terms actually added come…
langstring–Restrict to a two-letter language code, e.g. "ru".
limitinteger–Maximum number of results.
modestring–hybrid = both arms fused (best general choice); keyword = exact terms only, for names, codes and error strings; semantic = meaning-based, for vague or descriptive questions.
offsetinteger–Skip this many results — for a second page.
querystringyesThe search query.
sinceDaysinteger–Only pages published within this many days. Use for anything time-sensitive.
sitestring–Restrict to one host, e.g. "example.com".

No output schema declared.

No examples provided.

search_batch ~86

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.

NameTypeReqDescription
categorystring––
langstring––
limitinteger–Results per query.
queriesarrayyes–

No output schema declared.

No examples provided.

search_products ~294

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.

NameTypeReqDescription
best_per_productboolean–Collapse the same product across shops to its cheapest offer.
in_stockboolean–Only offers the shop states are in stock. Off by default: many shops never say.
limitinteger––
max_pricenumber–Upper bound.
min_pricenumber–Lower bound, in the shop's currency.
querystringyesWhat to find, in words a shopper would use.
shopstring–Restrict to one shop by host, e.g. citilink.ru.
sortstring––
vendorstring–Manufacturer, exact match.

No output schema declared.

No examples provided.

source_profile ~106

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.

NameTypeReqDescription
hoststringyesDomain, e.g. cbr.ru

No output schema declared.

No examples provided.

watch_query ~96

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.

NameTypeReqDescription
categorystring––
labelstring––
langstring––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Iskat — Russian-language web search for agents MCP server?

Iskat — Russian-language web search for agents is a hosted endpoint at https://iskat.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · iskat.io

# add to Claude Code
claude mcp add --transport http io-iskat-webdex 'https://iskat.io/mcp'
Common questions

What is the Iskat — Russian-language web search for agents MCP server?

Iskat — Russian-language web search for agents is an MCP server listed in the public MCP registry as io.iskat/webdex. Russian-language web search for agents: hybrid retrieval, product prices, full page text. This page covers its hosted endpoint (https://iskat.io/mcp).

Is the Iskat — Russian-language web search for agents MCP server safe to use?

Iskat — Russian-language web search for agents scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Iskat — Russian-language web search for agents MCP server expose?

Iskat — Russian-language web search for agents exposes 14 tools: search, search_products, fetch_page, fetch_pages, find_similar, and 9 more. Their descriptions and schemas cost roughly 1,414 tokens of context every time the server is loaded.

Does the Iskat — Russian-language web search for agents MCP server require authentication?

Its publisher declares no required credentials for Iskat — Russian-language web search for agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Iskat — Russian-language web search for agents MCP server still maintained?

Iskat — Russian-language web search for agents is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.