Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
eSIM Tabby is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Buy and manage travel eSIM data plans in the conversation. Pay by card (Stripe) or USDC over x402.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http esim-tabby-mcp https://esimtabby.com/mcp
# 2 — ask your agent for something these tools do
# search_esim_plans, get_plan_details, create_checkout and 8 more
eSIM Tabby costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ESAll 1 server
esimtabby1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http esim-tabby-mcp https://esimtabby.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find travel eSIM data plans available for a destination.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Country or region name, or ISO 3166-1 alpha-2 code |
| min_data_mb | no | Only plans with at least this much data | |
| max_duration_days | no | Only plans lasting at most this many days |
Full details of one eSIM plan, including current price.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | plan_id from search_esim_plans |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | plan_id from search_esim_plans |
| pay_with | string | no | 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 |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id from create_checkout |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id from create_checkout |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id of a fulfilled order |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id of a fulfilled eSIM to add data to |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id of the eSIM to add data to |
| plan_id | string | yes | plan_id from list_topup_options |
| pay_with | string | no | 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 |
How much data an active eSIM has used, and how much is left.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id of a fulfilled 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 refund automatically. A USDC payment has no on-chain refund rail, so the order becomes refund_pending and support returns the money by hand.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id of the order to cancel |
List this account's eSIM orders, newest first.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install eSIM Tabby or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.3.
0.1.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish eSIM Tabby can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.