Ext Ops Panel
Open dashboard
Comparison

jpyc-dev-reference vs io.github.acarchidi/agentforge

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). io.github.acarchidi/agentforge is an MCP server published by acarchidi. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
Marketplacejpyc-dev-referenceio.github.acarchidi/agentforge
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: 1.5.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

jpyc-dev-reference vs io.github.acarchidi/agentforge
Factjpyc-dev-referenceio.github.acarchidi/agentforge
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (agentforge-taupe.vercel.app/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12
Licence (differs)Not statedMIT
Repository (differs)github.com/mameta29/jpyc-skillgithub.com/acarchidi/agentforge
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

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

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.

io.github.acarchidi/agentforge

In its own words, on Official MCP Registry:

DeFi safety layer for AI agents: wallet safety, token risk, tx decode/simulate. 20 tools.

How to run each

jpyc-dev-reference As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install jpyc-dev-reference@claude-community

io.github.acarchidi/agentforge As a remote MCP server

Claude Code
claude mcp add --transport http agentforge https://agentforge-taupe.vercel.app/mcp

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

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

What it can do: jpyc-dev-reference · What it can do: io.github.acarchidi/agentforge · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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