stripe vs Korea Commerce: Naver Shopping, Olive Young, Daiso
stripe is a plugin bundle for AI coding tools published by stripe. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Korea Commerce: Naver Shopping, Olive Young, Daiso is an MCP server published by experimory-crypto. 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 |  stripe |  Korea Commerce: Naver Shopping, Olive Young, Daiso |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 0.1.2 Forks (GitHub): 387 Stars (GitHub): 2 059 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | stripe | Korea Commerce: Naver Shopping, Olive Young, Daiso |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 059 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 387 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (magenta-courser--korea-commerce-mcp.apify.actor/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/stripe/ai | github.com/experimory-crypto/naver-map-scraper-examples |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 18 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
stripe
Accept payments and grow your business. Stripe's agent plugin includes best practices, upgrade guidance, and our MCP server.
Korea Commerce: Naver Shopping, Olive Young, Daiso
Korean product prices and rankings from Naver Shopping, Olive Young and Daiso. Pay per result.
How to run each
stripe
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Korea Commerce: Naver Shopping, Olive Young, Daiso As a remote MCP server
claude mcp add --transport http korea-commerce https://magenta-courser--korea-commerce-mcp.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Korea Commerce: Naver Shopping, Olive Young, Daiso 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: stripe · What it can do: Korea Commerce: Naver Shopping, Olive Young, Daiso · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.