Ext Ops Panel
Open dashboard
Comparison

cairo vs io.github.opsloft/tariff-resolver

cairo is a plugin bundle for AI coding tools published by getklaim. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.opsloft/tariff-resolver is an MCP server published by opsloft. 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
Marketplacecairoio.github.opsloft/tariff-resolver
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
Downloads/month (npm): 458
Downloads/week (npm): 83
Forks (GitHub): 0
Stars (GitHub): 3
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

cairo vs io.github.opsloft/tariff-resolver
Factcairoio.github.opsloft/tariff-resolver
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (tariff-resolver)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/getklaim/cairogithub.com/opsloft/tariff-resolver
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

cairo

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

Diagnose your AI product's pricing system. Claude Code plugin that detects pricing model (tiered, usage-based, hybrid) and scores 6 maturity signals plus 6 usage-based deep checks

io.github.opsloft/tariff-resolver

In its own words, on Official MCP Registry:

US import duty research: HTS codes, Chapter 99 duties, MPF/HMF fees, landed cost. USITC data.

How to run each

cairo As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install cairo@claude-community

io.github.opsloft/tariff-resolver As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio tariff-resolver -- npx -y tariff-resolver

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: cairo · What it can do: io.github.opsloft/tariff-resolver · 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