Ext Ops Panel
Open dashboard
Comparison

bengo-toolkit vs US Code Federal Statutes

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). US Code Federal Statutes is an MCP server published by ecfr.io. 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

Where each is published
Marketplacebengo-toolkitUS Code Federal Statutes
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: 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

bengo-toolkit vs US Code Federal Statutes
Factbengo-toolkitUS Code Federal Statutes
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)0 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (uscode.ecfr.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)43Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/llamadrive/bengo-toolkitgithub.com/lrehmann/uscode-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 h ago

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

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 プラグイン — 裁判所書式入力・相続関係説明図・訴訟分析・法令検索・決定論的計算(交通事故・養育費・遺留分等)。

US Code Federal Statutes

In its own words, on Official MCP Registry:

Search and read U.S. Code statutes with legal and inline citations linking to uscode.ecfr.io.

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

US Code Federal Statutes As a remote MCP server

Claude Code
claude mcp add --transport http uscode https://uscode.ecfr.io/mcp

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

Only US Code Federal Statutes 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

Neither one's marketplaces publish the settings it asks for.

What it can do: bengo-toolkit · What it can do: US Code Federal Statutes · 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