Skills/PyPI/ozon-mcp-server

ozon-mcp-server@2.5.2

VERIFIED· not started

Publisher claims: "MCP server for Ozon Seller API + Performance API: 156 tools for prices, promos, ads, orders, returns and finance, with response sizes measured on a live account and trimmed from 476k to 64k tokens across a 16-response corpus" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher deviceingineering · publishing for 85 daysInstalls 410Last detonated 5 h ago
$claude mcp add ozon-mcp-server -- uvx ozon-mcp-server
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
MCP_AUTH_TOKENConfiguration, not credentials: DATA_DIR, HEALTH_CHECK_INTERVAL_MIN, OZON_MAX_RESPONSE_CHARS, OZON_TOOLSETS
Where it talks to
ozon.ru (its own)
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. It asks for MCP_AUTH_TOKEN and talks to ozon.ru. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets MCP_AUTH_TOKEN=ozon.ru -- uvx ozon-mcp-server

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-14 and scored it 91/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

MEDIUM
Python subprocess execution detectedtests/test_mcp_sse.py:51 · Python subprocess execution detectedproc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 10,335 lines in 59 files.

Cost to the agent

Instructions loaded
≈94 tok
1 file · 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 ozon-mcp-server@2.5.2 as of 5 h ago. This is the package itself, not its dependencies.