Ext Ops Panel
Open dashboard
Comparison

GovTribe 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.

GovTribe is a plugin bundle for AI coding tools published by GovTribe. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). 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-23. 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
MarketplaceGovTribeVivory Korea Data Gateway
Claude Code: claude-plugins-official Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

GovTribe vs Vivory Korea Data Gateway
FactGovTribeVivory Korea Data Gatewayno longer listed ·
Marketplaces that list it (differs)20
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-16Not published
Where it runs (differs)Remote server (govtribe.com/mcp)On your machine (vivory-mcp-korea)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)9Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/govtribe/claude-plugingithub.com/jayjodev/vivory-mcp
Changes in the last 7 days (differs)61
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 32 h agono 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

GovTribe

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

Government contracting research and capture workflows in Claude: opportunity and pipeline briefs, bid/no-bid and competitor analysis, price-to-win and proposal prep, powered by the GovTribe connector.

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

GovTribe As a Claude Code plugin

Claude Code
/plugin install govtribe@claude-plugins-official

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 GovTribe 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

The marketplaces of GovTribe publish no settings it asks for, so we do not compare settings.

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

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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