yandex360-mcp@0.2.0
VERIFIED· not startedPublisher claims: "MCP-сервер для сервисов Яндекс 360 (Вики и далее) — инструменты для AI-ассистентов." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
WIKI_TOKENConfiguration, not credentials: WIKI_ORG_ID, YANDEX360_ENABLE- Where it talks to
- no vendor host named in the codeAlso yandex.net — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names yandex.net as well as its own vendor. The guard injects WIKI_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-21 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
<summary><b>VS Code / GitHub Copilot</b></summary> Add to `.vscode/mcp.json`: ```json { "inputs": [ { "id": "wiki_token", "type": "promptString", "description":Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Claude Code</b></summary> Add to your project's `.mcp.json` (or run `claude mcp add`): ```json { "mcpServers": { "yandex360": { "type": "stdio", "coFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.`npx --yes @anthropic-ai/mcpb validate manifest.json`.Fix: Pin versions and sources; vendor anything fetched at install time.<summary><b>Claude Desktop</b></summary> **One-click install:** download the latest `yandex360-mcp-*.mcpb` from [Releases](https://github.com/pa1ch/yandex360-mcFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Cursor</b></summary> Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global): ```json { "mcpServers": { "yandex360": { "command": "uvx"Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for yandex360-mcp@0.2.0 as of 1 min ago. This is the package itself, not its dependencies.