esimtabby

endpoint

https://esimtabby.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is esimtabby live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is esimtabby free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does esimtabby have?

11 tools: search_esim_plans, list_topup_options, cancel_order, get_plan_details, create_checkout, pay_order, get_order_status, get_esim_activation, ….

Is esimtabby safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• search_esim_plans reads auth-required 6h ago

  Find travel eSIM data plans available for a destination.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "required": [
      "country"
    ],
    "properties": {
      "country": {
        "type": "string",
        "description": "Country or region name, or ISO 3166-1 alpha-2 code"
      },
      "min_data_mb": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Only plans with at least this much data"
      },
      "max_duration_days": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Only plans lasting at most this many days"
      }
    },
    "additionalProperties": false
  }

  arguments 37 lines copy
• list_topup_options reads auth-required 17h ago

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "description": "order_id of a fulfilled eSIM to add data to"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• cancel_order changes data auth-required never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "description": "order_id of the order to cancel"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• get_plan_details reads auth-required 6h ago

  Full details of one eSIM plan, including current price.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "plan_id"
    ],
    "properties": {
      "plan_id": {
        "type": "string",
        "description": "plan_id from search_esim_plans"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• create_checkout changes data auth-required never probed

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "required": [
      "plan_id"
    ],
    "properties": {
      "plan_id": {
        "type": "string",
        "description": "plan_id from search_esim_plans"
      },
      "pay_with": {
        "enum": [
          "card",
          "x402"
        ],
        "type": "string",
        "default": "card",
        "description": "How the buyer intends to pay. 'card' returns a hosted checkout link for a human to open in a browser. 'x402' returns an x402_url for a wallet tool to settle in USDC, with no browser step — only choose it if you have a wallet. An order keeps the rail it was first given: to pay an existing card order in USDC instead, cancel it and start a new one, so there are never two live ways to pay it."
      }
    },
    "additionalProperties": false
  }

  arguments 22 lines copy
• pay_order moves money auth-required never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "description": "order_id from create_checkout"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• get_order_status changes data auth-required never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "description": "order_id from create_checkout"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• get_esim_activation changes data auth-required never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "description": "order_id of a fulfilled order"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• create_topup_checkout changes data auth-required never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "required": [
      "order_id",
      "plan_id"
    ],
    "properties": {
      "plan_id": {
        "type": "string",
        "description": "plan_id from list_topup_options"
      },
      "order_id": {
        "type": "string",
        "description": "order_id of the eSIM to add data to"
      },
      "pay_with": {
        "enum": [
          "card",
          "x402"
        ],
        "type": "string",
        "default": "card",
        "description": "How the buyer intends to pay. 'card' returns a hosted checkout link for a human to open in a browser. 'x402' returns an x402_url for a wallet tool to settle in USDC, with no browser step — only choose it if you have a wallet. An order keeps the rail it was first given: to pay an existing card order in USDC instead, cancel it and start a new one, so there are never two live ways to pay it."
      }
    },
    "additionalProperties": false
  }

  arguments 27 lines copy
• list_my_orders reads auth-required never probed

  List this account's eSIM orders, newest first.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• get_esim_usage reads auth-required 6h ago

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

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "description": "order_id of a fulfilled order"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.