eSIM Tabby
REMOTE · ESIMTABBY.COM
Buy and manage travel eSIM data plans in the conversation. Pay by card (Stripe) or USDC over x402.
Available components
Last scanned (8 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 1 Sept 26 0
- Server version: 0.1.3 → 0.1.4 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- Tool “create_topup_checkout” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 91% → 100% ▲ functional
- Tool “pay_order” now declares an output schema ▲ functional
- Server version: 3.4.4 → 0.1.3 functional
- 18 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Aug 26 0
- Transport: unverified → pass ▲ security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 91 functional
- First check of Tool coverage: 100 functional
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 5 Nov 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 |
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 →
cancel_order Cancel and refund an 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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id of the order to cancel |
Structured output declared, but exposes no named fields.
No examples provided.
create_checkout Start a purchase ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| pay_with | string | – | 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_id | string | yes | plan_id from search_esim_plans |
Structured output declared, but exposes no named fields.
No examples provided.
create_topup_checkout Buy more data ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id of the eSIM to add data to |
| pay_with | string | – | 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_id | string | yes | plan_id from list_topup_options |
Structured output declared, but exposes no named fields.
No examples provided.
get_esim_activation Get eSIM activation QR code ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id of a fulfilled order |
| Name | Type | Req | Description |
|---|---|---|---|
| activation_code | string | yes | LPA activation string, for manual install |
| expires_at | – | yes | When the plan expires, in the provider's own format |
| iccid | string | yes | The eSIM's ICCID |
| instructions | string | yes | How to install the eSIM |
| order_id | string | yes | The order this eSIM belongs to |
| qr_code_url | string | yes | Image URL of the activation QR code |
| smdp_address | string | yes | SM-DP+ server address, for manual install |
No examples provided.
get_esim_usage Check data usage ~40
How much data an active eSIM has used, and how much is left.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id of a fulfilled order |
Structured output declared, but exposes no named fields.
No examples provided.
get_order_status Check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id from create_checkout |
Structured output declared, but exposes no named fields.
No examples provided.
get_plan_details Get plan details ~37
Full details of one eSIM plan, including current price.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | plan_id from search_esim_plans |
Structured output declared, but exposes no named fields.
No examples provided.
list_my_orders List my eSIM orders ~20
List this account's eSIM orders, newest first.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_topup_options List data top-ups ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id of a fulfilled eSIM to add data to |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
pay_order Pay for an order in USDC ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id from create_checkout |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | array | – | x402 payment requirements to satisfy |
| error | string | – | How to pay, for the 402 case |
| next_step | string | – | – |
| order_id | string | – | – |
| paid_with | string | – | – |
| result | string | – | – |
| status | string | – | – |
| transaction | string | – | On-chain transaction hash |
| x402Version | integer | – | – |
No examples provided.
search_esim_plans Search eSIM plans ~75
Find travel eSIM data plans available for a destination.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
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
claude mcp add --transport http com-esimtabby-esimtabby 'https://esimtabby.com/mcp'
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.