Ext Ops Panel
Open dashboard
Comparison

bengo-toolkit 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.

bengo-toolkit is a plugin bundle for AI coding tools published by llamadrive. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
Marketplacebengo-toolkitVivory Korea Data Gateway
Claude Code: claude-plugins-community Listed
Version: 3.8.2
Forks (GitHub): 5
Stars (GitHub): 6
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

bengo-toolkit vs Vivory Korea Data Gateway
Factbengo-toolkitVivory Korea Data Gatewayno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)60
Forks (GitHub) (differs)50
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (vivory-mcp-korea)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)43Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/llamadrive/bengo-toolkitgithub.com/jayjodev/vivory-mcp
Changes in the last 7 days22
First seen2026-10-112026-10-11

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

bengo-toolkit

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

Japanese law firm plugin for Claude Code — court template filling, family tree generation (相続関係説明図), legal document proofreading, lawsuit analysis, e-Gov law search, and deterministic legal calculators (traffic damages, child support, debt recalc, overtime, iryubun, property division, inheritance). Ships HMAC-chainedtamper-evident local audit logs (append-only JSONL with optional HMAC keying) recording which documents were processed, when, by which skill — without storing document contents. 日本の法律事務所向け Claude Code プラグイン — 裁判所書式入力・相続関係説明図・訴訟分析・法令検索・決定論的計算(交通事故・養育費・遺留分等)。

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

bengo-toolkit As a Claude Code plugin

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

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.

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 bengo-toolkit publish no settings it asks for, so we do not compare settings.

What it can do: bengo-toolkit · 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-community/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