bengo-toolkit vs LexAPI
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). LexAPI is an MCP server published by Lex-API. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  bengo-toolkit |  LexAPI |
|---|---|---|
| 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 | Listed Version: 0.1.3 Downloads/month (npm): 188 Downloads/week (npm): 40 Forks (GitHub): 0 Stars (GitHub): 3 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 | bengo-toolkit | LexAPI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 5 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@lexapi/mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 43 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/llamadrive/bengo-toolkit | github.com/lex-api/lexapi-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
bengo-toolkit
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 プラグイン — 裁判所書式入力・相続関係説明図・訴訟分析・法令検索・決定論的計算（交通事故・養育費・遺留分等）。
LexAPI
Search EUR-Lex, fetch parsed EU legislation and case law, explore the citation graph.
How to run each
bengo-toolkit As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install bengo-toolkit@claude-communityLexAPI As a local MCP server: npm package
claude mcp add --env "LEXAPI_API_KEY=<YOUR_LEXAPI_API_KEY>" --transport stdio lexapi-mcp -- npx -y @lexapi/mcpRequires: LEXAPI_API_KEY (secret)
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: LexAPI · 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.