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 Tracker (lite)

PYPI · YANDEX-TRACKER-MCP-LITE

Lean Yandex Tracker MCP: 9 tools, ~1.2k tokens of tool definitions, compact answers.

0 this week 66 Trust /100

Last scanned (17 hours ago)

Scores higher than 58% of PyPI 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 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 build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 836 tokens (~92/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 51

    First indexed and scored.

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 21 Nov 2026 · Analysed pypi/yandex-tracker-mcp-lite@0.1.1

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~745 tokens

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 →

Tool Tokens
add_comment ~54

Comment on a Tracker issue (markdown). summon: people to call into the issue (login, email, name or me).

NameTypeReqDescription
issuestringyes–
summonarray––
textstringyes–

No output schema declared.

No examples provided.

call_api ~105

Any Yandex Tracker API v3 request, for what the other tools don't cover: boards, sprints, worklogs, checklists, queues, components, projects. path is relative to /v3, e.g. 'boards', 'issues/DEV-1/worklog'. Docs: https://yandex.ru/support/tracker/en/about-api

NameTypeReqDescription
body–––
methodstringyes–
paramsobject––
pathstringyes–

No output schema declared.

No examples provided.

create_issue ~109

Create a Tracker issue in a queue (e.g. DEV). type: task, bug, epic, ... (queue default if empty). fields: any other field, e.g. {"parent": "DEV-1", "tags": ["x"], "priority": "critical"}.

NameTypeReqDescription
assigneestring––
descriptionstring––
fieldsobject––
queuestringyes–
summarystringyes–
typestring––

No output schema declared.

No examples provided.

get_issue ~92

Read one Tracker issue (e.g. DEV-123) with all its fields. In the same call: comments=N adds the last N comments, attachments=true lists files and downloads images to local paths you can open, changelog=true adds the last 50 field changes.

NameTypeReqDescription
attachmentsboolean––
changelogboolean––
commentsinteger––
issuestringyes–

No output schema declared.

No examples provided.

link_issues ~70

Link two Tracker issues. relationship: relates, depends on, is dependent by, is subtask for, is parent task for, duplicates, is duplicated by, is epic of, has epic.

NameTypeReqDescription
issuestringyes–
other_issuestringyes–
relationshipstring––

No output schema declared.

No examples provided.

search_issues ~95

Search Tracker issues. query is Tracker query language, e.g. 'Queue: DEV Assignee: me() Resolution: empty()', or a preset: mine (open, assigned to me), created (open, created by me), following. Returns one line per issue: key | status | assignee | updated | summary.

NameTypeReqDescription
limitinteger––
pageinteger––
querystringyes–

No output schema declared.

No examples provided.

transition_issue ~88

Move a Tracker issue to another status. Without status, lists the transitions available now. status matches a transition id, its name or the target status name. resolution when closing, e.g. fixed, won'tFix, duplicate.

NameTypeReqDescription
commentstring––
fieldsobject––
issuestringyes–
resolutionstring––
statusstring––

No output schema declared.

No examples provided.

update_issue ~105

Edit fields of a Tracker issue, e.g. {"summary": "...", "assignee": "me", "priority": "critical", "deadline": "2026-12-01", "tags": {"add": ["x"], "remove": ["y"]}, "followers": {"add": ["login"]}}. People: login, email, name or me. Status changes go through transition_issue.

NameTypeReqDescription
fieldsobjectyes–
issuestringyes–

No output schema declared.

No examples provided.

whoami ~27

Current Tracker user: login, name, email. Also a quick check that the token works.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Yandex Tracker (lite) MCP server?

Yandex Tracker (lite) runs locally as a PyPI package, launched with uvx yandex-tracker-mcp-lite. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · yandex-tracker-mcp-lite

# add to Claude Code
claude mcp add tonysafonov-yandex-tracker-mcp-lite -- uvx yandex-tracker-mcp-lite
Common questions

What is the Yandex Tracker (lite) MCP server?

Yandex Tracker (lite) is an MCP server listed in the public MCP registry as io.github.tonysafonov/yandex-tracker-mcp-lite. Lean Yandex Tracker MCP: 9 tools, ~1.2k tokens of tool definitions, compact answers. This page covers its PyPI package (yandex-tracker-mcp-lite).

Is the Yandex Tracker (lite) MCP server safe to use?

Yandex Tracker (lite) scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Yandex Tracker (lite) MCP server expose?

Yandex Tracker (lite) exposes 9 tools: whoami, search_issues, get_issue, add_comment, transition_issue, and 4 more. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.

Is the Yandex Tracker (lite) MCP server still maintained?

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

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

What did VerifyMCP test on the Yandex Tracker (lite) MCP server?

VerifyMCP ran 15 checks on Yandex Tracker (lite), covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Yandex Tracker (lite): Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.