ToolsMCP
yandex-per-result
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- johnisanerd (GitHub)
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 1.0.0 · updated
- Official links
Publisher’s description
Yandex rank tracking and bulk SERP data, billed per result, hosted MCP.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.0, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- johnisanerd (GitHub)
- Version observed
- 1.0.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.johnisanerd%2Fyandex-per-result/versions/1.0.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Search the web with sources | Publisher description mentions “serp”. | No connection check or task run. Capability is as described by the publisher. | Rule web-search matched: “serp”. Rule web-search. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://mcp.apify.com/?tools=johnvc/yandex-scrape-yandex-search-results-at-scale---per-result(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.johnisanerd/yandex-per-result
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.