Ext Ops Panel
Open dashboard
Comparison

nexusfeed-ltl-fuel-surcharges vs SAMOS e-commerce

nexusfeed-ltl-fuel-surcharges is a plugin bundle for AI coding tools published by NexusFeed. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SAMOS e-commerce is an MCP server published by samos-e.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacenexusfeed-ltl-fuel-surchargesSAMOS e-commerce
Claude Code: claude-plugins-community Listed
Version: 5fe1895
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.4
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

nexusfeed-ltl-fuel-surcharges vs SAMOS e-commerce
Factnexusfeed-ltl-fuel-surchargesSAMOS e-commerce
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (samos-e.com/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/nexusfeed/nexusfeed-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 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

nexusfeed-ltl-fuel-surcharges

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

Real-time LTL freight carrier fuel surcharge rates for AI agents. Covers 11 carriers (ODFL, Saia, Estes, ABF, R+L, TForce, XPO, SEFL, Averitt, FedEx, UPS). Every response includes a _verifiability block with extraction confidence, source timestamp, and evidence URL. Installed via uvx, authenticated with MCP_API_KEY env var.

SAMOS e-commerce

In its own words, on Official MCP Registry:

Track SAMOS parcels, estimate UK shipping, return and duty costs, and search SAMOS help.

How to run each

nexusfeed-ltl-fuel-surcharges As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install nexusfeed-ltl-fuel-surcharges@claude-community

SAMOS e-commerce As a remote MCP server

Claude Code
claude mcp add --transport http samos https://samos-e.com/api/mcp

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

Only SAMOS e-commerce 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

The marketplaces of SAMOS e-commerce publish no settings it asks for, so we do not compare settings.

What it can do: nexusfeed-ltl-fuel-surcharges · What it can do: SAMOS e-commerce · 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