Skip to content
eSIM Tabby logo

eSIM Tabby MCP server

Which servers in the official MCP registry are eSIM Tabby's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to eSIM Tabby

Whose server it is
  • Registry namecom.esimtabby/esimtabbyverified in the MCP registry

The registry name sits under esimtabby.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools11
  • Server calls itselfesimtabby
  • Server version0.1.4
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 193 ms.

Should an agent connect itNot proven either way yet
  • Its tools do search the travel eSIM catalogue from inside Claude, but not install an eSIM using the activation QR code.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "search the travel eSIM catalogue from inside Claude", the likely first call is search_esim_plans.
  • Keep approval on for pay_order: they delete, send or pay without saying so.
  • create_checkout, pay_order, create_topup_checkout, cancel_order change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer565 ms
  • Space in an agent's context≈ 1,678 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results11 of 11 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · search the travel eSIM catalogue from inside Claude
  • not sure · buy an eSIM plan by card or USDC in chat
  • cannot · install an eSIM using the activation QR code

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that delete, send or pay without telling the client so: pay_order
  • Tools that change data, on a server that answers without a sign-in: create_checkout, pay_order, create_topup_checkout, cancel_order

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers11 tools · read 2026-10-24
  • search_esim_plans

    Find travel eSIM data plans available for a destination.

  • get_plan_details

    Full details of one eSIM plan, including current price.

  • create_checkout

    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'…

  • pay_order

    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']…

  • get_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…

  • get_esim_activation

    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.

  • list_topup_options

    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.

  • create_topup_checkout

    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…

  • get_esim_usage

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

  • cancel_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…

  • list_my_orders

    List this account's eSIM orders, newest first.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://esimtabby.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.