MCP servers › io.github.bim-ba › ycli
MCP server · registry snapshot 2026-10-04
io.github.bim-ba/ycli
Yandex 360 Tracker, Wiki and Forms: read and write tools with honest read-only annotations. — the publisher's description
Summary
io.github.bim-ba/ycli is a local MCP server listed in the official MCP registry at version 0.49.1. We have not tested it. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Key facts
- Runs
- local package
- Transport
- standard input/output
- Package
- Docker (OCI), PyPI · listed version behind the latest release
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Topic
- productivity-and-docsAI-classified
- Last tested
- not tested
Worth knowing before you connect it
- The registry lists 0.49.1; 0.96.0 is newer (63 releases).
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Registry data
- snapshot 2026-10-04
- Package and repository
- checked 2026-10-06
Security testing
Has it been tested?
Feature #1It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Required inputs the publisher declares: YANDEX_ID_OAUTH_TOKEN (secret), YANDEX_ID_ORGANIZATION_ID.
What it is
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.49.1 on PyPI | Exists and can be installed | matches | PyPI · 2026-10-06 |
| Repository github.com/bim-ba/ycli | Opens publicly | matches | api.github.com · 2026-10-06 |
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.49.1
- Latest stable
- 0.96.0
- Status
- behind the latest release (63 releases, 3 days)
- Withdrawn
- no
Source: pypi.org · 2026-10-06. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-08 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-544bbda512051a812…
- License
- MIT
Source: the package registry · 2026-10-06.
Usage
- Downloads
- 9,047 in the last month
Source: pypistats.org · 2026-10-06.
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.bim-ba
- GitHub owner
- a personal account (bim-ba)
- Repository
- github.com/bim-ba/ycli
- Stars
- 4
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
Source: the registry entry and api.github.com · 2026-10-06.
Choosing
Common questions about io.github.bim-ba/ycli
Answered from the data aboveHas io.github.bim-ba/ycli been security tested?
Not yet. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Is the listed version current?
No. The registry lists 0.49.1; the latest stable release on PyPI is 0.96.0.
Where is the source code of io.github.bim-ba/ycli?
In github.com/bim-ba/ycli, which opens publicly.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.bim-ba/ycli: MCP server record.” Data checked 2026-10-06. https://protocolprobe.com/mcp/servers/io.github.bim-ba/ycli
Quoting is welcome with a link and the check date. Figures are valid for the date shown.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can authorize a full test.
Write to hello@protocolprobe.com · corrections log · methodology