Sells prepaid data-only travel eSIMs for 200+ countries: an assistant can compare plans, start a purchase, build multi-plan carts and check orders.
What you can do
Find and compare eSIM data plans by destination, cheapest first, with data, validity and USD price
Start a purchase for one plan and get a payment link
Build a single cart link from 2 to 6 plans for multi-country trips or several phones
Check whether a phone model is likely to support eSIM
Look up order status, data used and end date from the order number and purchase email
When to use it
Useful when a customer wants travel mobile data and you need to compare plans, confirm device compatibility, buy one or several eSIMs, or follow up on an existing order without leaving the conversation.
Requirements
Remote streamable HTTP endpoint; no local install, app or account. Buying requires the customer's email and payment through the returned link using the Machine Payments Protocol with a Stripe shared payment token. Order lookups need the order number and the email used at purchase.
Before you install
This server takes real payments: buy_esim and make_esim_cart lead to Stripe checkout, so confirm plan, price and email with the customer first. The customer's email is shared with the seller, and QR codes and install links are sent to it. Order status lookups require the order number plus that email.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.inboxesim%2Fesim/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Lists Inbox eSIM data plans for a destination (country, city, region such as Europe, or 'global'), cheapest first, with plan_id, data in GB, validity in days and price in USD. Data only, no phone number; works on unlocked eSIM phones.
Parametersmin_daysdestinationrequiredmin_data_gb
buy_esim
Buy a travel eSIM
Starts the purchase of one eSIM plan for the customer and returns a payment link. Pay it with the Machine Payments Protocol (HTTP 402, Stripe shared payment token) to complete the order. Before calling, confirm the plan, the price and the email with the customer, and get their agreement to the terms: By buying, the customer asks for the eSIM to be sent at once and accepts the terms (https://inboxesim.com/terms): the 14-day right to withdraw ends once the eSIM is installed. An eSIM that was never installed or used can be refunded within 30 days from its order page, less the payment fee (in full within 14 days in the EU and UK).
For a trip to several countries (or several phones): turns 2 to 6 plan_ids from find_esim_plans into one cart link. The customer opens it, checks the eSIMs and pays once on Stripe; each eSIM comes in its own QR email and can be refunded on its own. 3 or more eSIMs in one cart are 5% off. Nothing is bought until the customer pays on the page.
Parametersplan_idsrequired
check_esim_device
Check a phone for eSIM
Says whether a phone model is likely to take an eSIM (likely, unlikely or check), from the model name, with how to be sure on the phone itself. Call it before buy_esim when the customer is unsure.
Parametersdevicerequired
get_order_status
Get an eSIM order's status
Where an Inbox eSIM order is (awaiting_payment, preparing, ready_to_install, installed, in_use, ended, refunded, cancelled, with_support), with data used, the end date and the order page. Needs the order number and the email it was bought with.
Parametersorder_idrequiredcustomer_emailrequired
Version history
1
v1.0.0LatestOct 29, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.