Ya Tracker MCP Server

ya-tracker-mcp PyPI v0.8.2

Published by keemor — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Yandex Tracker API — issues, projects, boards, sprints, worklog and more

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 135

Each tool and what it can reach — statically extracted from the published source.

  • create_issuenetwork egress
  • create_issue_typenetwork egress
  • add_checklist_itemno sensitive capability
  • add_commentno sensitive capability
  • add_entity_checklist_itemno sensitive capability
  • add_entity_commentno sensitive capability
  • add_presetno sensitive capability
  • add_worklogno sensitive capability
  • bulk_list_linksno sensitive capability
  • bulk_moveno sensitive capability
Show 125 more tools ↓
  • bulk_transitionno sensitive capability
  • bulk_updateno sensitive capability
  • bulk_update_entitiesno sensitive capability
  • configure_cacheno sensitive capability
  • count_issuesno sensitive capability
  • create_autoactionno sensitive capability
  • create_boardno sensitive capability
  • create_componentno sensitive capability
  • create_cycle_time_widgetno sensitive capability
  • create_dashboardno sensitive capability
  • create_entityno sensitive capability
  • create_entity_linkno sensitive capability
  • create_external_linkno sensitive capability
  • create_filterno sensitive capability
  • create_from_presetno sensitive capability
  • create_macrono sensitive capability
  • create_priorityno sensitive capability
  • create_queueno sensitive capability
  • create_queue_versionno sensitive capability
  • create_resolutionno sensitive capability
  • create_sprintno sensitive capability
  • create_statusno sensitive capability
  • create_triggerno sensitive capability
  • delete_attachmentno sensitive capability
  • delete_boardno sensitive capability
  • delete_checklistno sensitive capability
  • delete_checklist_itemno sensitive capability
  • delete_commentno sensitive capability
  • delete_entityno sensitive capability
  • delete_entity_attachmentno sensitive capability
  • delete_entity_checklist_itemno sensitive capability
  • delete_entity_commentno sensitive capability
  • delete_entity_linkno sensitive capability
  • delete_external_linkno sensitive capability
  • delete_linkno sensitive capability
  • delete_macrono sensitive capability
  • delete_queueno sensitive capability
  • delete_queue_tagno sensitive capability
  • delete_worklogno sensitive capability
  • entity_changelogno sensitive capability
  • find_assigneeno sensitive capability
  • get_autoactionno sensitive capability
  • get_autoaction_logsno sensitive capability
  • get_boardno sensitive capability
  • get_bulk_failed_issuesno sensitive capability
  • get_bulk_statusno sensitive capability
  • get_cache_statusno sensitive capability
  • get_componentno sensitive capability
  • get_entityno sensitive capability
  • get_entity_settingsno sensitive capability
  • get_filterno sensitive capability
  • get_issueno sensitive capability
  • get_macrono sensitive capability
  • get_myselfno sensitive capability
  • get_presetno sensitive capability
  • get_queueno sensitive capability
  • get_queue_user_permissionsno sensitive capability
  • get_team_memberno sensitive capability
  • get_triggerno sensitive capability
  • get_trigger_logsno sensitive capability
  • get_userno sensitive capability
  • import_commentno sensitive capability
  • import_fileno sensitive capability
  • import_issueno sensitive capability
  • import_linkno sensitive capability
  • issue_changelogno sensitive capability
  • issue_overviewno sensitive capability
  • link_issuesno sensitive capability
  • list_attachmentsno sensitive capability
  • list_autoactionsno sensitive capability
  • list_board_columnsno sensitive capability
  • list_boardsno sensitive capability
  • list_checklistno sensitive capability
  • list_commentsno sensitive capability
  • list_componentsno sensitive capability
  • list_entity_attachmentsno sensitive capability
  • list_entity_commentsno sensitive capability
  • list_entity_linksno sensitive capability
  • list_external_applicationsno sensitive capability
  • list_external_linksno sensitive capability
  • list_field_categoriesno sensitive capability
  • list_global_fieldsno sensitive capability
  • list_issue_typesno sensitive capability
  • list_linksno sensitive capability
  • list_macrosno sensitive capability
  • list_presetsno sensitive capability
  • list_prioritiesno sensitive capability
  • list_queue_fieldsno sensitive capability
  • list_queue_tagsno sensitive capability
  • list_queue_versionsno sensitive capability
  • list_queuesno sensitive capability
  • list_resolutionsno sensitive capability
  • list_sprintsno sensitive capability
  • list_statusesno sensitive capability
  • list_teamno sensitive capability
  • list_transitionsno sensitive capability
  • list_triggersno sensitive capability
  • list_usersno sensitive capability
  • list_worklogno sensitive capability
  • move_issueno sensitive capability
  • queue_overviewno sensitive capability
  • remove_presetno sensitive capability
  • restore_queueno sensitive capability
  • search_entitiesno sensitive capability
  • search_issuesno sensitive capability
  • search_worklogno sensitive capability
  • sync_all_directoriesno sensitive capability
  • sync_directoryno sensitive capability
  • transition_issueno sensitive capability
  • update_boardno sensitive capability
  • update_checklist_itemno sensitive capability
  • update_commentno sensitive capability
  • update_componentno sensitive capability
  • update_entityno sensitive capability
  • update_entity_checklist_itemno sensitive capability
  • update_entity_commentno sensitive capability
  • update_entity_metricsno sensitive capability
  • update_entity_settingsno sensitive capability
  • update_filterno sensitive capability
  • update_issueno sensitive capability
  • update_key_resultsno sensitive capability
  • update_macrono sensitive capability
  • update_queue_permissionsno sensitive capability
  • update_triggerno sensitive capability
  • update_worklogno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.8.2 latest A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ya-tracker-mcp/badge.svg)](https://mcptrustchecker.com/registry/ya-tracker-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ya-tracker-mcp"><img src="https://mcptrustchecker.com/registry/ya-tracker-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ya-tracker-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ya-tracker-mcp --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow