Yandex Cloud Docs MCP
Provides offline, read-only full-text search over a local Yandex Cloud documentation checkout via MCP, with ranked search, line-numbered excerpts, and index status tools.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
selivanov-tech
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
search_yandex_cloud_docsFull-text search over the local, offline Yandex Cloud documentation index. For English questions, translate core concepts to Russian before searching. Returns ranked local paths and line-numbered excerpts.
read_yandex_cloud_docRead up to 400 numbered lines from a document returned by search_yandex_cloud_docs. Paths are relative to the configured documentation root.
yandex_cloud_docs_statusReport the local documentation Git revision, index revision, file count, and whether the explicit index refresh command is needed.
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
3/3 tools missing one or more hints — search_yandex_cloud_docs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_yandex_cloud_doc (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); yandex_cloud_docs_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool inputs are validated
2/3 tool handlers declare input schemas (67%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Shell command execution
13 child_process calls — runs shell commands
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/selivanov-tech/yandex-cloud-docs-mcp)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check