io.github.DeviceIngineering/ozon-mcp-server
PYPI · OZON-MCP-SERVER
Ozon Seller & Performance API, 156 tools; responses trimmed 476k to 64k tokens.
Available components
Last scanned (3 hours ago)
Scores higher than 92% of PyPI servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 37 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to DeviceIngineering/ozon-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 41 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 7207 tokens (~46/item across 156 items; 156 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ozon_seller_action_products_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 156 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 13 Oct 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.83 functional
- 12 Oct 26 +18
- Malware scan: unverified → pass ▲ security
- Stability: 0.80 → pass security
- 6 Oct 26 −3
- Stability: fail → 0.80 functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 95 to 99.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 89 to 92.
- 29 Sept 26 +5
No change was recorded against any check on this day. Stability & Change Management went from 50 to 85.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed pypi/ozon-mcp-server@2.5.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | DeviceIngineering/ozon-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/DeviceIngineering/ozon-mcp-server/.github/workflows/publish.yml@refs/tags/v2.5.2 |
| Rekor log index | 2722376980 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b01c51b919cbe8f87a4226bbeb185cbb32ebb13097be4fa9877c7bc271fec39d |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 37 packages
| Packages resolved | 37 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ozon_stock_on_warehouses ~52
Stock and turnover at Ozon warehouses, via turnover/stocks — the old endpoint was removed (остатки на складах).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
ozon_supply_order_counters ~25
Supply order counters by status (счётчики поставок).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ozon_supply_order_get ~35
FBO supply order details, 1-50 (детали поставки).
| Name | Type | Req | Description |
|---|---|---|---|
| order_ids | array | yes | – |
No output schema declared.
No examples provided.
ozon_supply_order_timeslots ~33
Available FBO supply timeslots (таймслоты).
| Name | Type | Req | Description |
|---|---|---|---|
| supply_order_id | integer | yes | – |
No output schema declared.
No examples provided.
ozon_supply_orders ~60
FBO supply orders (v3), returns order_ids; details via ozon_supply_order_get (заявки на поставку).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| states | array | – | status codes 1-8, default all |
No output schema declared.
No examples provided.
ozon_warehouse_list ~40
Seller FBS warehouses (склады).
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | compact (default) trims heavy fields; full returns the raw API response |
No output schema declared.
No examples provided.
How do I install the io.github.DeviceIngineering/ozon-mcp-server server?
io.github.DeviceIngineering/ozon-mcp-server runs locally as a PyPI package, launched with uvx ozon-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ozon-mcp-server
claude mcp add deviceingineering-ozon-mcp-server -- uvx ozon-mcp-server
What is the io.github.DeviceIngineering/ozon-mcp-server server?
io.github.DeviceIngineering/ozon-mcp-server is listed in the public MCP registry as io.github.DeviceIngineering/ozon-mcp-server. Ozon Seller & Performance API, 156 tools; responses trimmed 476k to 64k tokens. This page covers its PyPI package (ozon-mcp-server).
Is the io.github.DeviceIngineering/ozon-mcp-server server safe to use?
io.github.DeviceIngineering/ozon-mcp-server scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.DeviceIngineering/ozon-mcp-server server expose?
io.github.DeviceIngineering/ozon-mcp-server exposes 156 tools: ozon_list_shops, ozon_actions_list, ozon_actions_candidates, ozon_actions_products, ozon_actions_activate, and 151 more. Their descriptions and schemas cost roughly 7,207 tokens of context every time the server is loaded.
Is the io.github.DeviceIngineering/ozon-mcp-server server still maintained?
io.github.DeviceIngineering/ozon-mcp-server is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.DeviceIngineering/ozon-mcp-server server under?
io.github.DeviceIngineering/ozon-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.