eSIM Tabby

com.esimtabbyPublished by esimtabby.comOfficial publisherv0.1.3Updated Oct 24, 2026

Buy and manage travel eSIM data plans in the conversation. Pay by card (Stripe) or USDC over x402.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search travel eSIM data plans, start and pay for orders by card or USDC, and retrieve activation details and usage.

What you can do
Provides eleven tools for buying and managing travel eSIM data plans in conversation. The assistant can search plans for a destination, view a plan's details and current price, create a checkout, check order status, and fetch the QR code and activation details. It can also list top-up options, buy a top-up for an existing eSIM, check remaining data usage, cancel an order, and list the account's orders.
When to use it
Useful when a user wants to buy or top up a travel data plan without leaving the chat, or needs activation details, remaining data, or order history for an eSIM bought through this service.
Requirements
A remote MCP endpoint at esimtabby.com over streamable HTTP; no packages, environment variables, or headers are declared. Payment by card goes through a hosted Stripe checkout page; paying in USDC over x402 requires an MCP client that signs x402 payments itself.
Before you install
This server spends money: create_checkout and create_topup_checkout start purchases, and pay_order settles payment in USDC. get_order_status and get_esim_activation are not read-only and can advance an order's state. cancel_order refunds card payments automatically, but a USDC payment has no on-chain refund route, and cancellation is refused once the eSIM profile is installed. Activation details include a QR code.

Installation

In SourceWeft

  1. Open eSIM Tabby in the dashboard and add it to a workspace.
  2. 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.esimtabby%2Fesimtabby/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "esim-tabby": {
      "type": "http",
      "url": "https://esimtabby.com/mcp"
    }
  }
}

Tools

11

search_esim_plans

Search eSIM plans

Find travel eSIM data plans available for a destination.

Parameterscountryrequiredmin_data_mbmax_duration_days

get_plan_details

Get plan details

Full details of one eSIM plan, including current price.

Parametersplan_idrequired

create_checkout

Start a purchase

Start a purchase — the step after the user picks a plan from search_esim_plans. Call it with that plan's plan_id (get_plan_details shows the current price first). Returns an order_id and where to pay, on the rail you asked for: 'card' (the default) returns a checkout_url — a hosted Stripe page for a human to open in a browser; once they say they've paid, call get_order_status to confirm and carry on to the QR code. 'x402' returns an x402_url for a wallet to settle in USDC, with no browser step — only choose it if you actually hold a wallet. Never accepts payment details — a card is entered on the hosted page, and a wallet signs for itself. Calling it again for the same plan reuses the pending order (reused: true) instead of creating a duplicate.

Parametersplan_idrequiredpay_with

pay_order

Pay for an order in USDC

Pay for an order in USDC over x402, without opening a browser. Only for an MCP client that signs x402 payments itself: call it once for the payment requirements, then repeat the call carrying the signed payment in _meta['x402/payment'] and it settles and starts the eSIM. If your wallet is a separate tool, make an x402 request to the order's x402_url instead — this tool cannot take a payment on a wallet tool's behalf.

Parametersorder_idrequired

get_order_status

Check order status

Check an order. Call this after the user says they've paid. Not read-only: an order still in progress is advanced first — payment is confirmed and the provider order placed or collected — so the status can change as a result of calling this.

Parametersorder_idrequired

get_esim_activation

Get eSIM activation QR code

Get the QR code and activation details for a purchased eSIM. Not read-only: like get_order_status, an order that is not ready yet is advanced first, so this can change the order's state.

Parametersorder_idrequired

list_topup_options

List data top-ups

Data top-ups that can be added to an eSIM the user already has. A top-up extends the existing eSIM — same QR code, nothing to re-install. Not every plan is reloadable; this returns an empty list when none apply.

Parametersorder_idrequired

create_topup_checkout

Buy more data

Buy more data for an eSIM the user already has — the step after list_topup_options. Call it with the order_id of the fulfilled eSIM and a plan_id chosen from list_topup_options. The top-up lands on the existing eSIM: same QR code, nothing to re-install. Returns a new order_id and where to pay, exactly like create_checkout: 'card' returns a checkout_url for a human to open, confirmed via get_order_status; 'x402' returns an x402_url for a wallet to settle in USDC. Never accepts payment details — a card is entered on the hosted page, and a wallet signs for itself.

Parametersplan_idrequiredorder_idrequiredpay_with

get_esim_usage

Check data usage

How much data an active eSIM has used, and how much is left.

Parametersorder_idrequired

cancel_order

Cancel and refund an order

Cancel an order and refund it. Only possible while the eSIM is uninstalled. Once the profile has been installed on a device the provider refuses to take it back, and this returns an error instead — send the user to support. Card payments refund automatically. A USDC payment has no on-chain refund rail, so the order becomes `refund_pending` and support returns the money by hand.

Parametersorder_idrequired

list_my_orders

List my eSIM orders

List this account's eSIM orders, newest first.

Takes no parameters.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

83% 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
  • 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.