jpyc-dev-reference vs Boj
jpyc-dev-reference is a plugin bundle for AI coding tools published by Mameta29. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Boj is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  jpyc-dev-reference |  Boj |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.4 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
| Fact | jpyc-dev-reference | Boj |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (gateway.pipeworx.io/boj/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mameta29/jpyc-skill | github.com/pipeworx-io/mcp-boj |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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
jpyc-dev-reference
Developer reference for JPYC, a JPY-pegged stablecoin (日本円ステーブルコイン) deployed on Ethereum, Polygon, and Avalanche. Provides contract addresses, ERC20 functions, EIP-3009 gasless transfer signatures, EIP-2612 permit, admin/role operations (mint, burn, pause, blocklist), EIP712 domain configuration, type hashes, error messages, and TypeScript/viem code examples.
Boj
Bank of Japan (BOJ) / Japan monetary MCP. Keyless.
How to run each
jpyc-dev-reference As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install jpyc-dev-reference@claude-communityBoj As a remote MCP server
claude mcp add --transport http boj https://gateway.pipeworx.io/boj/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Boj has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of jpyc-dev-reference nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: jpyc-dev-reference · What it can do: Boj · 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.