Ext Ops Panel
Open dashboard
Comparison

Inbox eSIM vs trvl

Inbox eSIM is an MCP server published by inboxesim.com. Marketplaces we read that list it: 1 (Official MCP Registry). trvl is an MCP server published by MikkoParkkola. 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 eSIMtrvl
Official MCP Registry Listed
Version: 1.1.0
No figure published
Not marked · First seen
Listed
Version: 1.27.0
Forks (GitHub): 8
Stars (GitHub): 93
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.27.0
Downloads/month (npm): 1 586
Downloads/week (npm): 371
Forks (GitHub): 8
Stars (GitHub): 93
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 trvl
FactInbox eSIMtrvl
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub93
Forks (GitHub) (differs)No figure on GitHub8
Last release (differs)2026-11-08Not published
Where it runs (differs)Remote server (inboxesim.com/mcp)On your machine (ghcr.io/mikkoparkkola/trvl:1.27.0)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published22, secrets among them: 15
Licence (differs)Not statedPolyForm-Noncommercial-1.0.0
Repository (differs)Not statedgithub.com/mikkoparkkola/trvl
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 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

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

trvl

In its own words, on Official MCP Registry:

Door-to-door travel MCP + CLI: flights, hotels, trains, cars, ferries. No API keys, Go binary.

How to run each

Inbox eSIM As a remote MCP server

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

trvl As a local MCP server: Docker image

Claude Code
claude mcp add --env "AFKLM_KEY=<YOUR_AFKLM_KEY>" --env "AFKL_KLM_COOKIES=<YOUR_AFKL_KLM_COOKIES>" --env "DISTRIBUSION_API_KEY=<YOUR_DISTRIBUSION_API_KEY>" --env "FOURSQUARE_API_KEY=<YOUR_FOURSQUARE_API_KEY>" --env "GEOAPIFY_API_KEY=<YOUR_GEOAPIFY_API_KEY>" --env "OPENTRIPMAP_API_KEY=<YOUR_OPENTRIPMAP_API_KEY>" --env "SERPAPI_KEY=<YOUR_SERPAPI_KEY>" --env "SKYSCANNER_API_KEY=<YOUR_SKYSCANNER_API_KEY>" --env "TICKETMASTER_API_KEY=<YOUR_TICKETMASTER_API_KEY>" --env "TRANSAVIA_API_KEY=<YOUR_TRANSAVIA_API_KEY>" --env "TRAVELPAYOUTS_TOKEN=<YOUR_TRAVELPAYOUTS_TOKEN>" --env "TRVL_MCP_OAUTH_CLIENT_SECRET=<YOUR_TRVL_MCP_OAUTH_CLIENT_SECRET>" --env "TRVL_MCP_READ_TOKEN=<YOUR_TRVL_MCP_READ_TOKEN>" --env "TRVL_MCP_TOKEN=<YOUR_TRVL_MCP_TOKEN>" --env "TRVL_MCP_WRITE_TOKEN=<YOUR_TRVL_MCP_WRITE_TOKEN>" --transport stdio trvl -- docker run -i --rm -e AFKLM_KEY -e AFKL_KLM_COOKIES -e DISTRIBUSION_API_KEY -e FOURSQUARE_API_KEY -e GEOAPIFY_API_KEY -e OPENTRIPMAP_API_KEY -e SERPAPI_KEY -e SKYSCANNER_API_KEY -e TICKETMASTER_API_KEY -e TRANSAVIA_API_KEY -e TRAVELPAYOUTS_TOKEN -e TRVL_MCP_OAUTH_CLIENT_SECRET -e TRVL_MCP_READ_TOKEN -e TRVL_MCP_TOKEN -e TRVL_MCP_WRITE_TOKEN ghcr.io/mikkoparkkola/trvl:1.27.0

Requires: AFKLM_KEY (secret), AFKL_KLM_COOKIES (secret), DISTRIBUSION_API_KEY (secret), FOURSQUARE_API_KEY (secret), GEOAPIFY_API_KEY (secret), OPENTRIPMAP_API_KEY (secret), SERPAPI_KEY (secret), SKYSCANNER_API_KEY (secret), TICKETMASTER_API_KEY (secret), TRANSAVIA_API_KEY (secret), TRAVELPAYOUTS_TOKEN (secret), TRVL_MCP_OAUTH_CLIENT_SECRET (secret), TRVL_MCP_READ_TOKEN (secret), TRVL_MCP_TOKEN (secret), TRVL_MCP_WRITE_TOKEN (secret)

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

Only Inbox eSIM 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 Inbox eSIM publish no settings it asks for, so we do not compare settings.

What it can do: Inbox eSIM · What it can do: trvl · 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