Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

eSIM Tabby

REMOTE · ESIMTABBY.COM · SCANNED SEP 20

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

Available components

remote · esimtabby.com 92
+1 this week 92 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1374 tokens (~124/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the eSIM Tabby MCP server?

eSIM Tabby is a hosted endpoint at https://esimtabby.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · esimtabby.com

# add to Claude Code
claude mcp add --transport http com-esimtabby-esimtabby 'https://esimtabby.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-esimtabby-esimtabby": {
      "url": "https://esimtabby.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-esimtabby-esimtabby": {
      "type": "http",
      "url": "https://esimtabby.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-esimtabby-esimtabby]
url = "https://esimtabby.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-esimtabby-esimtabby": {
      "type": "remote",
      "url": "https://esimtabby.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-esimtabby-esimtabby --url 'https://esimtabby.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-esimtabby-esimtabby:
    url: "https://esimtabby.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-esimtabby-esimtabby": {
      "Transport": "http",
      "Url": "https://esimtabby.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-esimtabby-esimtabby -t streamable-http -u 'https://esimtabby.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-esimtabby-esimtabby": {
      "type": "http",
      "url": "https://esimtabby.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://esimtabby.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=esimtabby.com CN=WE1,O=Google Trust Services,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA256 ace339068cb4d8ec139dcd343a734394
SANs: esimtabby.com, *.esimtabby.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of esimtabby.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
esimtabby.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://esimtabby.com/.well-known/oauth-protected-resource/mcp" 

Bearer resource_metadata="https://esimtabby.com/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://esimtabby.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://esimtabby.com/mcp
Authorisation server https://scientific-cafe-65.authkit.app/

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://esimtabby.com/mcp Verified 200
http (plaintext) http://esimtabby.com/mcp HTTPS enforced 301 https://esimtabby.com/mcp
MCP tools · 11 exposed · ~1,211 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_order ~104

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.

NameTypeReqDescription
order_idstringyesorder_id of the order to cancel

Structured output declared, but exposes no named fields.

No examples provided.

create_checkout ~310

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.

NameTypeReqDescription
pay_withstring–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 choos…
plan_idstringyesplan_id from search_esim_plans

Structured output declared, but exposes no named fields.

No examples provided.

create_topup_checkout ~284

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.

NameTypeReqDescription
order_idstringyesorder_id of the eSIM to add data to
pay_withstring–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 choos…
plan_idstringyesplan_id from list_topup_options

Structured output declared, but exposes no named fields.

No examples provided.

get_esim_activation ~67

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.

NameTypeReqDescription
order_idstringyesorder_id of a fulfilled order
NameTypeReqDescription
activation_codestringyesLPA activation string, for manual install
expires_at–yesWhen the plan expires, in the provider's own format
iccidstringyesThe eSIM's ICCID
instructionsstringyesHow to install the eSIM
order_idstringyesThe order this eSIM belongs to
qr_code_urlstringyesImage URL of the activation QR code
smdp_addressstringyesSM-DP+ server address, for manual install

No examples provided.

get_esim_usage ~40

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

NameTypeReqDescription
order_idstringyesorder_id of a fulfilled order

Structured output declared, but exposes no named fields.

No examples provided.

get_order_status ~73

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.

NameTypeReqDescription
order_idstringyesorder_id from create_checkout

Structured output declared, but exposes no named fields.

No examples provided.

get_plan_details ~37

Full details of one eSIM plan, including current price.

NameTypeReqDescription
plan_idstringyesplan_id from search_esim_plans

Structured output declared, but exposes no named fields.

No examples provided.

list_my_orders ~20

List this account's eSIM orders, newest first.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_topup_options ~80

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.

NameTypeReqDescription
order_idstringyesorder_id of a fulfilled eSIM to add data to
NameTypeReqDescription
resultarrayyes–

No examples provided.

pay_order ~121

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.

NameTypeReqDescription
order_idstringyesorder_id from create_checkout
NameTypeReqDescription
acceptsarray–x402 payment requirements to satisfy
errorstring–How to pay, for the 402 case
next_stepstring––
order_idstring––
paid_withstring––
resultstring––
statusstring––
transactionstring–On-chain transaction hash
x402Versioninteger––

No examples provided.

search_esim_plans ~75

Find travel eSIM data plans available for a destination.

NameTypeReqDescription
countrystringyesCountry or region name, or ISO 3166-1 alpha-2 code
max_duration_days––Only plans lasting at most this many days
min_data_mb––Only plans with at least this much data
NameTypeReqDescription
resultarrayyes–

No examples provided.

Common questions

What is the eSIM Tabby MCP server?

eSIM Tabby is an MCP server listed in the public MCP registry as com.esimtabby/esimtabby. Buy and manage travel eSIM data plans in the conversation. Pay by card (Stripe) or USDC over x402. This page covers its hosted endpoint (https://esimtabby.com/mcp).

Is the eSIM Tabby MCP server safe to use?

eSIM Tabby scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the eSIM Tabby MCP server expose?

eSIM Tabby exposes 11 tools: search_esim_plans, get_plan_details, create_checkout, pay_order, get_order_status, and 6 more. Their descriptions and schemas cost roughly 1,211 tokens of context every time the server is loaded.

Does the eSIM Tabby MCP server require authentication?

Yes. eSIM Tabby asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the eSIM Tabby MCP server still maintained?

eSIM Tabby is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.