Ext Ops Panel
Open dashboard
Comparison

Dappier Remote vs Vivory Korea Data Gateway

Vivory Korea Data Gateway is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

Dappier Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vivory Korea Data Gateway is an MCP server published by jayjodev. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceDappier RemoteVivory Korea Data Gateway
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Removed on 2026-10-23
Version: 0.6.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

Dappier Remote vs Vivory Korea Data Gateway
FactDappier RemoteVivory Korea Data Gatewayno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dappier.com/mcp)On your machine (vivory-mcp-korea)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/jayjodev/vivory-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 403 (4 h ago)no remote endpoint we check

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of Vivory Korea Data Gateway

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

Its card, with similar plugins by marketplace

What each says it does

Dappier Remote

In its own words, on Docker MCP Catalog:

Enable fast, free real-time web search and access premium data from trusted media brands—news, financial markets, sports, entertainment, weather, and more. Build powerful AI agents with Dappier.

Vivory Korea Data Gateway

In its own words, on Official MCP Registry:

DEPRECATED v0.6.0 — migrate to vivory-mcp-verification (Korean verdict tools included).

How to run each

Dappier Remote As a remote MCP server

Claude Code
claude mcp add --transport http dappier-remote https://mcp.dappier.com/mcp

Requires: DAPPIER_REMOTE_API_KEY (secret)

Vivory Korea Data Gateway

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Dappier Remote 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

Only Dappier Remote asks for

  • DAPPIER_REMOTE_API_KEY (secret)

Only Vivory Korea Data Gateway asks for

  • VIVORY_API_BASE
  • VIVORY_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Dappier Remote · What it can do: Vivory Korea Data Gateway · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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