eSIM Tabby MCP server
Buy and manage travel eSIM data plans in the conversation. Pay by card (Stripe) or USDC over x402.
Little public usage data yet
Reviews
Write oneNobody has reviewed eSIM Tabby yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
eSIM Tabby tools (11, 5 write)
write = sends, deletes, buys or postscancel_orderwrite actionFreeCancel 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.
create_checkoutwrite actionFreeStart 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.
create_topup_checkoutwrite actionFreeBuy 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.
get_esim_activationFreeGet 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.
get_esim_usageFreeHow much data an active eSIM has used, and how much is left.
get_order_statuswrite actionFreeCheck 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.
get_plan_detailsFreeFull details of one eSIM plan, including current price.
list_my_ordersFreeList this account's eSIM orders, newest first.
list_topup_optionsFreeData 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.
pay_orderwrite actionFreePay 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.
search_esim_plansFreeFind travel eSIM data plans available for a destination.
Public scan report
scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1246ms20/20
- Tool poisoning11 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
- Maintenanceno repository listed3/15
- Maintainer identityverified namespace with website, no repo4/10
Findings (2)
- highWrite-action tools reachable without authentication
auth.open-write - lowNo source repository listed
maint.no-repo
Install directly
claude mcp add --transport http esimtabby https://esimtabby.com/mcp
eSIM Tabby: common questions
- Is eSIM Tabby MCP server safe?
- With care: it is graded C, so read the findings first (60/100). Read the eSIM Tabby safety report
- How do I install eSIM Tabby?
- It runs remotely at esimtabby.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does eSIM Tabby need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is eSIM Tabby maintained?
- The latest release is v0.1.3.
- Is eSIM Tabby up?
- 100% of our last 20 checks got an answer. We check remote servers about four times a day.
- What can I use instead of eSIM Tabby?
- Servers from other publishers that do the same job: Esimfly MCP server, Loki Mode MCP server and Ecommerce Trends MCP server. Compare all eSIM Tabby alternatives.
Alternatives to eSIM Tabby
Same job from other publishers: the closest match first, then the best rated.
- EsimflyeSIMfly Business API: search eSIM plans, check usage, diagnose eSIMs, optionally order (confirmed)not reviewedGrowingA
- Loki ModeAutonomous spec-to-product coding-agent CLI with an MCP server exposing 36 tools over stdio.not reviewedEstablishedB
- Ecommerce Trends MCPProduct and category demand trend volume over time, with growth signals. Free key at trendsmcp.ainot reviewedGrowingA
- TempGuru Event StaffingPlan W-2 event staffing from 345 catalog entries; a coordinator confirms each order.not reviewedGrowingA
- MCP ServerTyped record store + hybrid search over MCP: deterministic lookups + semantic memory, per-customer.not reviewedGrowingB