io.github.pa1ch/yandex360-mcp
PYPI · YANDEX360-MCP · SCANNED SEP 20
MCP server for Yandex 360 services (Wiki, and more) — tools for AI assistants.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 52 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Instruction-quality not yet verified: the AI judgement didn't run.Unverified
- Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety0
- Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.Unverified
- Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
- Manipulation not yet verified: our capture carried no tool text for a judge to read, so we will not certify text no model has read as clean.Unverified
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.pa1ch/yandex360-mcp server?
io.github.pa1ch/yandex360-mcp runs locally as a PyPI package, launched with uvx yandex360-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · yandex360-mcp
claude mcp add pa1ch-yandex360-mcp -- uvx yandex360-mcp
{
"mcpServers": {
"pa1ch-yandex360-mcp": {
"command": "uvx",
"args": [
"yandex360-mcp"
]
}
}
} {
"servers": {
"pa1ch-yandex360-mcp": {
"command": "uvx",
"args": [
"yandex360-mcp"
]
}
}
} codex mcp add pa1ch-yandex360-mcp -- uvx yandex360-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pa1ch-yandex360-mcp": {
"type": "local",
"command": [
"uvx",
"yandex360-mcp"
],
"enabled": true
}
}
} openclaw mcp add pa1ch-yandex360-mcp --command uvx --arg yandex360-mcp
mcp_servers:
pa1ch-yandex360-mcp:
command: "uvx"
args: ["yandex360-mcp"] {
"McpServers": {
"pa1ch-yandex360-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"yandex360-mcp"
]
}
}
} assistant mcp add pa1ch-yandex360-mcp -t stdio -c uvx -a yandex360-mcp
{
"mcpServers": {
"pa1ch-yandex360-mcp": {
"command": "uvx",
"args": [
"yandex360-mcp"
]
}
}
} 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 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 · Analysed pypi/yandex360-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
The sandbox run completed and this package exposed no tools.
What is the io.github.pa1ch/yandex360-mcp server?
io.github.pa1ch/yandex360-mcp is listed in the public MCP registry as io.github.pa1ch/yandex360-mcp. MCP server for Yandex 360 services (Wiki, and more), tools for AI assistants. This page covers its PyPI package (yandex360-mcp).
Is the io.github.pa1ch/yandex360-mcp server safe to use?
io.github.pa1ch/yandex360-mcp scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.pa1ch/yandex360-mcp server expose?
io.github.pa1ch/yandex360-mcp exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the io.github.pa1ch/yandex360-mcp server still maintained?
io.github.pa1ch/yandex360-mcp 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.
What licence is the io.github.pa1ch/yandex360-mcp server under?
io.github.pa1ch/yandex360-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.