Skills/PyPI/ya-tracker-mcp

ya-tracker-mcp@0.8.2

VERIFIED· not started

Publisher claims: "MCP server for Yandex Tracker API — issues, projects, boards, sprints, worklog and more" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher keemor · publishing for 260 daysInstalls 140Last detonated 1 h ago
$claude mcp add ya-tracker-mcp -- uvx ya-tracker-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
TRACKER_API_KEYYA_TRACKER_TOKENConfiguration, not credentials: TRACKER_ORG_ID, YA_TRACKER_ORG_ID
Where it talks to
no vendor host named in the codeAlso yandex.ru — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names yandex.ru as well as its own vendor. The guard injects TRACKER_API_KEY, YA_TRACKER_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx ya-tracker-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-21 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsthoughts/shared/handoffs/general/2026-03-12_12-16_v030-field-categories.yaml:32 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- publish_workflow: "rm old dist → uv build → source .env.local → uv publish --token $PYPI_TOKEN"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
LOW
Instructs the agent to modify its persistent memory or instruction filesthoughts/shared/handoffs/general/2026-03-31_22-02_deep-explore-claude-md.yaml:8 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction filegoal: Deep exploration of ya-tracker-mcp codebase and CLAUDE.md updateFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathsthoughts/shared/handoffs/general/2026-03-07_22-15_v020-release-140-tools.yaml:35 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- pypi_auth: "PyPI token stored in .env.local as PYPI_TOKEN, used via uv publish --token"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsthoughts/shared/handoffs/general/2026-03-08_22-15_bugfixes-and-presets.yaml:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- pypi_workflow: "rm old dist files → uv build → source .env.local → uv publish --token $PYPI_TOKEN"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsthoughts/shared/handoffs/general/2026-03-12_14-30_v031-extra-fields-docs.yaml:36 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- pypi_publish_flow: "rm -rf dist && uv build && source .env.local && uv publish --token $PYPI_TOKEN"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈808 tok
2 files · 59 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for ya-tracker-mcp@0.8.2 as of 38 min ago. This is the package itself, not its dependencies.