Ext Ops Panel
Open dashboard
Comparison

Wingspan vs io.github.89rat/code402

Wingspan is a plugin bundle for AI coding tools published by wingspanHQ. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). io.github.89rat/code402 is an MCP server published by 89rat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceWingspanio.github.89rat/code402
Claude Code: claude-plugins-official Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
No figure published
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

Wingspan vs io.github.89rat/code402
FactWingspanio.github.89rat/code402
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.wingspan.app/v3/mcp)Remote server (rail.hcrb.in/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/wingspanhq/mcp-claude-plugingithub.com/89rat/m2m-exchange
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetResponded 7 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

Wingspan

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

Ask Claude about the contractors you pay through Wingspan, what you owe them, and what is holding up a payment, then onboard contractors and log payments as drafts, with a preview before anything is written. Requires a Wingspan account; bundles the Wingspan MCP server (OAuth on first use).

io.github.89rat/code402

In its own words, on Official MCP Registry:

Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.

How to run each

Wingspan As a Claude Code plugin

Claude Code
/plugin install wingspan@claude-plugins-official

io.github.89rat/code402 As a remote MCP server

Claude Code
claude mcp add --transport http code402 https://rail.hcrb.in/mcp

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

Only io.github.89rat/code402 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: Wingspan · What it can do: io.github.89rat/code402 · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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