Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Horoshop MCP

MCPB · HOROSHOP-MCP.MCPB

Unofficial server for Horoshop (Хорошоп) stores: catalog, orders, SEO, feeds, admin. 118 tools.

Available components

+3 this week 31 Trust /100

Last scanned (18 hours ago)

Scores higher than 73% of MCPB servers

Category E-commerce

Trust breakdown (7 categories)

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 Security23
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs were checked across the 103 of 103 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 31 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency42
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Maintenance history not yet determined.Unverified
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 3 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

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.

  • 22 Oct 26 0
    • Maintenance: pass → unverified ▼ functional
  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 47. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 40. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 +4
    • Stability: unverified → 0.30 ▲ functional
Diagnostics

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 22 Oct 2026 · Analysed mcpb/https://github.com/IgorShutko/horoshop-mcp/releases/download/v0.3.0/horoshop-mcp.mcpb@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 103 packages
Packages resolved 103
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 118 exposed · ~57,318 tokens partial

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 →

Tool Tokens
horoshop_customer_groups_export ~238

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_delivery_export ~144

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_delivery_types ~140

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_hooks_subscribe ~198

No description provided.

NameTypeReqDescription
eventstringyes–
storestring––
target_urlstringyes–

No output schema declared.

No examples provided.

horoshop_hooks_unsubscribe ~89

No description provided.

NameTypeReqDescription
idintegeryes–
storestring––
target_urlstringyes–

No output schema declared.

No examples provided.

horoshop_icons_export ~149

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_list_stores ~172

No description provided.

NameTypeReqDescription
allowLargeboolean––

No output schema declared.

No examples provided.

horoshop_orders_get ~1,111

No description provided.

NameTypeReqDescription
additionalDataboolean––
allowLargeboolean––
fromstring––
idsarray––
limitinteger––
offsetinteger––
status–––
storestring––
tostring––

No output schema declared.

No examples provided.

horoshop_orders_get_statuses ~206

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_orders_update ~435

No description provided.

NameTypeReqDescription
ordersarrayyes–
returnStockboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_pages_export ~237

No description provided.

NameTypeReqDescription
allowLargeboolean––
parentinteger––
storestring––

No output schema declared.

No examples provided.

horoshop_payment_export ~142

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_payment_methods ~145

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_price_levels_export ~218

No description provided.

NameTypeReqDescription
allowLargeboolean––
storestring––

No output schema declared.

No examples provided.

horoshop_product_set_import ~103

No description provided.

NameTypeReqDescription
itemsarrayyes–
storestring––

No output schema declared.

No examples provided.

horoshop_product_set_remove ~86

No description provided.

NameTypeReqDescription
articlesarrayyes–
storestring––

No output schema declared.

No examples provided.

horoshop_users_export ~197

No description provided.

NameTypeReqDescription
allowLargeboolean––
fromstring––
limitinteger––
offsetinteger––
storestring––
tostring––

No output schema declared.

No examples provided.

horoshop_users_import ~155

No description provided.

NameTypeReqDescription
storestring––
usersarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the Horoshop MCP server?

Horoshop MCP ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

mcpb · horoshop-mcp.mcpb

Download bundle

The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.

Common questions

What is the Horoshop MCP server?

Horoshop MCP is listed in the public MCP registry as io.github.IgorShutko/horoshop-mcp. Unofficial server for Horoshop (Хорошоп) stores: catalog, orders, SEO, feeds, admin. 118 tools. This page covers its MCPB bundle (https://github.com/IgorShutko/horoshop-mcp/releases/download/v0.3.0/horoshop-mcp.mcpb).

Is the Horoshop MCP server safe to use?

Horoshop MCP scores 31 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 licence is the Horoshop MCP server under?

Horoshop MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.