io.github.johnisanerd/yandex-search
REMOTE · MCP.APIFY.COM · SCANNED SEP 20
Yandex search results, images, and SERP data via the Apify Yandex Search Scraper, hosted MCP.
Available components
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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 733 tokens (~733/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 2 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.
How do I install the io.github.johnisanerd/yandex-search MCP server?
io.github.johnisanerd/yandex-search is a hosted endpoint at https://mcp.apify.com/?tools=johnvc/Scrape-Yandex, 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 · mcp.apify.com
claude mcp add --transport http johnisanerd-yandex-search 'https://mcp.apify.com/?tools=johnvc/Scrape-Yandex'
{
"mcpServers": {
"johnisanerd-yandex-search": {
"url": "https://mcp.apify.com/?tools=johnvc/Scrape-Yandex"
}
}
} {
"servers": {
"johnisanerd-yandex-search": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/Scrape-Yandex"
}
}
} [mcp_servers.johnisanerd-yandex-search] url = "https://mcp.apify.com/?tools=johnvc/Scrape-Yandex"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"johnisanerd-yandex-search": {
"type": "remote",
"url": "https://mcp.apify.com/?tools=johnvc/Scrape-Yandex",
"enabled": true
}
}
} openclaw mcp add johnisanerd-yandex-search --url 'https://mcp.apify.com/?tools=johnvc/Scrape-Yandex' --transport streamable-http
mcp_servers:
johnisanerd-yandex-search:
url: "https://mcp.apify.com/?tools=johnvc/Scrape-Yandex" {
"McpServers": {
"johnisanerd-yandex-search": {
"Transport": "http",
"Url": "https://mcp.apify.com/?tools=johnvc/Scrape-Yandex"
}
}
} assistant mcp add johnisanerd-yandex-search -t streamable-http -u 'https://mcp.apify.com/?tools=johnvc/Scrape-Yandex'
{
"mcpServers": {
"johnisanerd-yandex-search": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/Scrape-Yandex"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 20 Sept 2026 · Probed https://mcp.apify.com/?tools=johnvc/Scrape-Yandex
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.apify.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 3 Jul 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 33947021329345fc779537cd9a338fd |
| SANs: *.apify.com, apifier.com, *.apifier.com, apify.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.apify.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| apify.com. | present | 54503 | 13 | Verified |
| mcp.apify.com. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations"
Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.apify.com/?tools=johnvc/Scrape-Yandex | Verified | 200 | |
| http (plaintext) | http://mcp.apify.com/?tools=johnvc/Scrape-Yandex | HTTPS enforced | 301 | https://mcp.apify.com:443/?tools=johnvc/Scrape-Yandex |
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 →
No tool schema has been captured from this endpoint yet.
What is the io.github.johnisanerd/yandex-search MCP server?
io.github.johnisanerd/yandex-search is an MCP server listed in the public MCP registry as io.github.johnisanerd/yandex-search. Yandex search results, images, and SERP data via the Apify Yandex Search Scraper, hosted MCP. This page covers its hosted endpoint (https://mcp.apify.com/?tools=johnvc/Scrape-Yandex).
Is the io.github.johnisanerd/yandex-search MCP server safe to use?
io.github.johnisanerd/yandex-search scores 72 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.
Does the io.github.johnisanerd/yandex-search MCP server require authentication?
Yes. io.github.johnisanerd/yandex-search asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.johnisanerd/yandex-search MCP server still maintained?
io.github.johnisanerd/yandex-search is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.