Ext Ops Panel
Open dashboard
Comparison

io.github.mrfentmen/usps-mcp vs Easypost

io.github.mrfentmen/usps-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). Easypost is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplaceio.github.mrfentmen/usps-mcpEasypost
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 417
Downloads/week (npm): 79
Not marked · First seen
Listed
Version: 0.2.1
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

io.github.mrfentmen/usps-mcp vs Easypost
Factio.github.mrfentmen/usps-mcpEasypost
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-11-01
Where it runs (differs)On your machine (usps-mcp)Remote server (gateway.pipeworx.io/easypost/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 21, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/mrfentmen/premium-mcpsgithub.com/pipeworx-io/mcp-easypost
Changes in the last 7 days00
First seen (differs)2026-10-172026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

io.github.mrfentmen/usps-mcp

In its own words, on Official MCP Registry:

USPS shipping, tracking, address validation, and label creation.

Easypost

In its own words, on Official MCP Registry:

EasyPost MCP — multi-carrier shipping rates + package tracking (easypost.com)

How to run each

io.github.mrfentmen/usps-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "USPS_API_KEY=<YOUR_USPS_API_KEY>" --env "USPS_PASSWORD=<YOUR_USPS_PASSWORD>" --transport stdio usps-mcp -- npx -y usps-mcp

Requires: USPS_API_KEY (secret), USPS_PASSWORD (secret)

Easypost As a remote MCP server

Claude Code
claude mcp add --transport http easypost https://gateway.pipeworx.io/easypost/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Only Easypost 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

Only io.github.mrfentmen/usps-mcp asks for

  • USPS_API_KEY (secret)
  • USPS_API_URL
  • USPS_PASSWORD (secret)
  • USPS_USERNAME

Only Easypost asks for

  • PIPEWORX_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.mrfentmen/usps-mcp · What it can do: Easypost · Compare two other plugins

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