Ext Ops Panel
Open dashboard
Comparison

Inbox eSIM vs io.github.warpfreight/warp-agent-mcp

Inbox eSIM is an MCP server published by inboxesim.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.warpfreight/warp-agent-mcp is an MCP server published by warpfreight. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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
MarketplaceInbox eSIMio.github.warpfreight/warp-agent-mcp
Official MCP Registry Listed
Version: 1.1.0
No figure published
Not marked · First seen
Listed
Version: 0.20.1
Downloads/month (npm): 2 375
Downloads/week (npm): 1 359
Forks (GitHub): 2
Stars (GitHub): 8
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.25.1
Downloads/month (npm): 2 375
Downloads/week (npm): 1 359
Forks (GitHub): 2
Stars (GitHub): 8
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

Inbox eSIM vs io.github.warpfreight/warp-agent-mcp
FactInbox eSIMio.github.warpfreight/warp-agent-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub8
Forks (GitHub) (differs)No figure on GitHub2
Last release (differs)2026-11-08 (better)2026-11-03 (worse)
Where it runs (differs)Remote server (inboxesim.com/mcp)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/warpfreight/warp-agent-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-282026-10-11
Endpoint at the last check (differs)Responded 15 h agoResponded 10 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

Inbox eSIM

In its own words, on Official MCP Registry:

Travel eSIMs for 200+ countries: compare 100+ eSIM brands' prices and buy a plan (MPP, Stripe).

io.github.warpfreight/warp-agent-mcp

In its own words, on Official MCP Registry:

Quote, book, and track LTL, FTL, cargo van, and box-truck freight via the Warp API.

How to run each

Inbox eSIM As a remote MCP server

Claude Code
claude mcp add --transport http esim https://inboxesim.com/mcp

io.github.warpfreight/warp-agent-mcp As a remote MCP server

Claude Code
claude mcp add --transport http warp-agent-mcp https://mcp.wearewarp.com/api/mcp

Requires: WARP_API_KEY (secret)

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

Both endpoints responded at the last daily 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 Inbox eSIM publish no settings it asks for, so we do not compare settings.

What it can do: Inbox eSIM · What it can do: io.github.warpfreight/warp-agent-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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