daiso vs Korean Retail Data (Daiso, Musinsa)
daiso is an MCP server published by hmmhmmhm. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Korean Retail Data (Daiso, Musinsa) is an MCP server published by cocomoon612. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  daiso |  Korean Retail Data (Daiso, Musinsa) |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 1.3.1 Downloads/month (npm): 2 110 Downloads/week (npm): 256 Forks (GitHub): 30 Stars (GitHub): 347 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | daiso | Korean Retail Data (Daiso, Musinsa) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 347 | No figure on GitHub |
| Forks (GitHub) (differs) | 30 | No figure on GitHub |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | On your machine (daiso) | Remote server (mcp.apify.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hmmhmmhm/daiso-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-11-10 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 19 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
daiso
Korean retail and cinema MCP server, CLI, and Codex Skill for Daiso, convenience stores, marts, Olive Young, and theaters
Korean Retail Data (Daiso, Musinsa)
Daiso Korea products with real units sold, Musinsa K-fashion rankings and size-fit reviews.
How to run each
daiso
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Korean Retail Data (Daiso, Musinsa)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Korean Retail Data (Daiso, Musinsa) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: daiso · What it can do: Korean Retail Data (Daiso, Musinsa) · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.