horoshop
io.github.ecomkit-com-ua/horoshop
About horoshop
horoshop is an MCP server published by the GitHub account ecomkit-com-ua. MCP server for the Horoshop e-commerce API — orders, catalog, customers, webhooks
It runs on your own machine: your AI client starts it from the npm package horoshop-mcp at version 0.1.1.
It asks for one secret: HOROSHOP_PASSWORD. Give it a key with the least access that still works.
It also needs HOROSHOP_DOMAIN and HOROSHOP_LOGIN set before it starts.
Version 0.1.1 was published on 3 September 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
HOROSHOP_DOMAIN | Yes | No | Store domain, e.g. myshop.com.ua (with or without https://) |
HOROSHOP_LOGIN | Yes | No | Login of a dedicated admin account created in the Horoshop panel (Налаштування → Адміни) |
HOROSHOP_PASSWORD | Yes | Yes | Password of that admin account. Horoshop has no API keys, so admin credentials are used |
HOROSHOP_READONLY | No | No | Set to 1 to hide every tool that writes to the store. Recommended for a first run |
HOROSHOP_TIMEOUT_MS | No | No | Request timeout in milliseconds |
HOROSHOP_MAX_RESPONSE_BYTES | No | No | Cap on a single tool response; larger exports are truncated with a note |
HOROSHOP_INSECURE_HTTP | No | No | Set to 1 to use plain http instead of https (dev stores only) |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/ecomkit-com-ua/horoshop-mcp |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 1 secret: HOROSHOP_PASSWORD |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account ecomkit-com-ua |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | horoshop-mcp@0.1.1 runs nothing at install |
| Code red flags | Pass | Read 15 files in horoshop-mcp@0.1.1: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 15 files, including comments and the README |
Popularity & health: 53 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
0 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.ecomkit-com-ua/horoshop |
|---|---|
| Publisher | GitHub account ecomkit-com-ua |
| How the name is verified | Name verified via GitHub account ecomkit-com-ua. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm horoshop-mcp 0.1.1 (stdio) |
| Version | 0.1.1 |
| Published | |
| Last updated | |
| Source repository | https://github.com/ecomkit-com-ua/horoshop-mcp |
| Website | https://ecomkit.com.ua/instrumenty/ |
| Category | Search & web (assigned by keyword rule, not by hand) |
Related servers in Search & web
- A1 Yandex KIT MCP7/7A1 Yandex KIT MCP server for the Yandex KIT e-commerce API:…
Aide3/3AI customer service: set up an AI support agent, search knowledge,…- Shopify7/7Shopify Admin API tools: products, media, orders, customers,…
- Shopify Admin MCP7/7MCP server for the Shopify Admin API: products, orders, customers,…
- shopify-admin7/7Manage products, orders, customers, inventory, and store configuration
- retailcrm-mcp7/7MCP server for RetailCRM — orders, customers management via API v5.