Ext Ops Panel
Open dashboard
Comparison

tenders vs Korea Commerce: Naver Shopping, Olive Young, Daiso

tenders is a plugin bundle for AI coding tools published by lexsocket. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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

Where each is published
MarketplacetendersKorea Commerce: Naver Shopping, Olive Young, Daiso
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

tenders vs Korea Commerce: Naver Shopping, Olive Young, Daiso
FacttendersKorea Commerce: Naver Shopping, Olive Young, Daiso
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.lexsocket.ai)Remote server (magenta-courser--korea-commerce-mcp.apify.actor/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/lexsocket/tendersgithub.com/experimory-crypto/naver-map-scraper-examples
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-11
Endpoint at the last check (differs)No HTTP response at the last check (22 h ago)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

tenders

In its own words, on Claude Code: claude-plugins-community:

Search, analyze, and monitor European public tenders (TED + 18 national sources) and EU legislation — directly from your AI assistant.

Korea Commerce: Naver Shopping, Olive Young, Daiso

In its own words, on Official MCP Registry:

Korean product prices and rankings from Naver Shopping, Olive Young and Daiso. Pay per result.

How to run each

tenders As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tenders@claude-community

Korea Commerce: Naver Shopping, Olive Young, Daiso As a remote MCP server

Claude Code
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 the endpoint of Korea Commerce: Naver Shopping, Olive Young, Daiso responded at the last daily 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: tenders · 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/anthropics/claude-plugins-community/blob/HEAD/.claude-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.

Where the data comes from: how the catalog is built