mcp-server-yandex-market-seller@0.6.0
VERIFIED· not startedPublisher claims: "MCP server for Yandex Market Partner API — orders, offers, prices, stocks, analytics" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
YM_AUTH_TYPEYM_TOKENConfiguration, not credentials: YM_BUSINESS_ID, YM_CAMPAIGN_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 the honeypot saw
- 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 YM_AUTH_TYPE, YM_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
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-09 and scored it 89/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 deviationsStatic findings
(["chat-file-send", "123", "/tmp/file.txt"], "action", "chat_file_send"),Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."params_json": json.dumps({"chat_id": 1, "file_path": "/etc/passwd"}),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…use merge commits. ALWAYS rebase.** - **CRITICAL: НИКОГДА не читать содержимое `.env` файлов** — запрещено использовать `cat`, `Read`, `grep`, `head`, `tail` и любы…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
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 mcp-server-yandex-market-seller@0.6.0 as of 5d ago. This is the package itself, not its dependencies.