Skip to main content

eSIM Tabby

com.esimtabby/esimtabbyVersion 0.1.3

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

Status

Responds173 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 13:55 UTC
Latency
173 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://esimtabby.com/mcpResponds173 ms
No sign-in

Claude Code

claude mcp add --transport http esimtabby https://esimtabby.com/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: esimtabby
Remote MCP server URL: https://esimtabby.com/mcp

Cursor

{
  "mcpServers": {
    "esimtabby": {
      "url": "https://esimtabby.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"esimtabby","type":"http","url":"https://esimtabby.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

11 tools

Tools of eSIM Tabby
Read-only
Idempotent
Open world
cancel_orderCancel 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.YesNoNoYes
create_checkoutStart 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.NoNoNoYes
create_topup_checkoutBuy 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.NoNoNoYes
get_esim_activationGet 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.NoNoYesYes
get_esim_usageHow much data an active eSIM has used, and how much is left.NoYesNot declaredNo
get_order_statusCheck 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.NoNoYesYes
get_plan_detailsFull details of one eSIM plan, including current price.NoYesNot declaredNo
list_my_ordersList this account's eSIM orders, newest first.NoYesNot declaredNo
list_topup_optionsData 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.NoYesNot declaredNo
pay_orderPay 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.NoNoNoYes
search_esim_plansFind travel eSIM data plans available for a destination.NoYesNot declaredNo

Details

Registry status
Active
Published
Aug 21, 2026
Updated
Aug 21, 2026
Repository
Not given
Categories (suggested)
Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing