74
/ 100
22 days ago
glama

Yandex Tracker MCP Server

Exposes Yandex Tracker's REST API v3 as tools for LLM clients, enabling issue management and queue operations via natural language.

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: TRACKER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configTRACKER_AUTH_SCHEMEOAuth (default) or Bearer (e.g. IAM)
configTRACKER_BASE_URLdefault https://api.tracker.yandex.net/v3; change for self-hosted
configTRACKER_ORG_HEADERX-Org-ID (Yandex 360, default) or X-Cloud-Org-ID (Yandex Cloud)
configTRACKER_ORG_IDOrganisation ID from [Tracker administration → Organisations](https://tracker.yandex.com/admin/orgs)
🔐 secretTRACKER_TOKENOAuth token (see below)
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/dchuhin-tracker-mcp-server-1ugvil)](https://m8ven.ai/mcp/dchuhin-tracker-mcp-server-1ugvil)
commit: c844abcbb1878dcfb18aa04226021c0ec44cddd3
code hash: fe053d11ff38ff65c841463e03183bb583ef10dde91de64910eb45726ca9467f
verified: 6/18/2026, 11:11:43 AM
view raw JSON →