Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Yandex 360 (ycli)

OCI · GHCR.IO/BIM-BA/YCLI · 2 COMPONENTS

Yandex 360 Tracker, Wiki and Forms: read and write tools with honest read-only annotations.

Available components

oci · ghcr.io/bim-ba/ycli 10 pypi · yandex-cli 39
0 this week 10 Trust /100

Last scanned (1 hour ago)

Scores higher than 23% of OCI servers

Category Project Management

Trust breakdown (7 categories)

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • 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 25 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: 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.

Changelog

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.

  • 4 Nov 26 0
    • Package version: 0.53.1 → 0.142.0 functional
  • 3 Nov 26 0
    • Package version: 0.53.1 → 0.142.0 functional
  • 2 Nov 26 0
    • Package version: 0.53.1 → 0.142.0 functional
  • 1 Nov 26 0
    • Package version: 0.53.1 → 0.142.0 functional
  • 30 Oct 26 0
    • Package version: 0.53.1 → 0.142.0 functional
  • 28 Oct 26 0
    • Package version: 0.53.1 → 0.142.0 functional
  • 26 Oct 26 0
    • Package version: 0.53.1 → 0.142.0 functional
  • 24 Oct 26 0
    • Package version: 0.53.1 → 0.142.0 functional
Diagnostics

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 5 Nov 2026 · Analysed oci/ghcr.io/bim-ba/ycli@0.142.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Yandex 360 (ycli) MCP server?

Yandex 360 (ycli) runs locally as a container image, launched with docker run --rm -i -e YANDEX_ID_OAUTH_TOKEN -e YANDEX_ID_ORGANIZATION_ID ghcr.io/bim-ba/ycli:0.142.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/bim-ba/ycli

# add to Claude Code
claude mcp add bim-ba-ycli -- docker run --rm -i -e YANDEX_ID_OAUTH_TOKEN -e YANDEX_ID_ORGANIZATION_ID ghcr.io/bim-ba/ycli:0.142.0

This image reads YANDEX_ID_OAUTH_TOKEN and YANDEX_ID_ORGANIZATION_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Yandex 360 (ycli) MCP server?

Yandex 360 (ycli) is an MCP server listed in the public MCP registry as io.github.bim-ba/ycli. Yandex 360 Tracker, Wiki and Forms: read and write tools with honest read-only annotations. This page covers its container image (ghcr.io/bim-ba/ycli).

Is the Yandex 360 (ycli) MCP server safe to use?

Yandex 360 (ycli) scores 10 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.

Is the Yandex 360 (ycli) MCP server still maintained?

Yandex 360 (ycli) is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Yandex 360 (ycli) MCP server under?

Yandex 360 (ycli) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.