Ext Ops Panel
Open dashboard
Comparison

Wingspan vs itr-agent

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). itr-agent is an MCP server published by Sagargupta16. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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
MarketplaceWingspanitr-agent
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: 0.7.0
Forks (GitHub): 2
Stars (GitHub): 10
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 itr-agent
FactWingspanitr-agent
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0 (worse)10 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last release (differs)2026-10-16 (worse)2026-11-14 (better)
Where it runs (differs)Remote server (api.wingspan.app/v3/mcp)On your machine (itr-agent)
Transport (differs)Streamable HTTPstdio
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/sagargupta16/itr-agent
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-11-13
Endpoint at the last check (differs)Responded 9 h agono remote endpoint we check

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).

itr-agent

In its own words, on Official MCP Registry:

Local-first Indian income tax filing agent: ITR form, tax computation, 26AS/AIS reconciliation

How to run each

Wingspan As a Claude Code plugin

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

itr-agent As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio itr-agent -- npx -y itr-agent

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

Only Wingspan 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: itr-agent · 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