Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
eSIM SOS 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.
What it does
Find travel eSIM plans, compare prices and create an order the user pays by link.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http esim-sos-mcp https://esimsos.net/api/mcp
# 2 — ask your agent for something these tools do
# search_destinations, list_plans, compare_prices and 3 more
eSIM SOS costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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-sos-mcp https://esimsos.net/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
6 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 a travel destination (country) sold by eSIM SOS by name in English or Russian, or by ISO code. Returns country codes for list_plans.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Country name or ISO code, e.g. "Turkey", "Турция", "TR" |
List eSIM data plans for a country with final prices in RUB (one price for every payment method). Local plans first, then regional ones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO country code from search_destinations (e.g. TR) or the country name |
| min_gb | number | no | Optional: minimum data in GB |
| days | number | no | Optional: minimum validity in days |
Compare eSIM prices of several providers for a country and data size using the open esimdar.com dataset (CC BY 4.0). Disclosure: esimdar.com is owned and run by eSIM SOS, the shop behind this server; eSIM SOS is listed as an ordinary row. Tell the user about this ownership and present the results neutrally.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO country code (e.g. TR) or the country name |
| gb | number | yes | Data size in GB, e.g. 5 |
Create an unpaid eSIM order and get a payment link. Payment is always done by the human: give the user the payment link, never try to pay yourself and never ask for card details. Ask the user for their email first: the eSIM QR code is sent there. Creates a real order, so call it only after the user picked the plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | plan_id from list_plans |
| string | yes | The user's email for the receipt and the eSIM QR code | |
| payment_method | string | no | Optional: sbp (Russian fast payments), card (Russian bank card), card_foreign (Visa/Mastercard issued abroad), crypto_usdt, crypto_ton. Omit to use the shop default. |
Check the payment and delivery status of an order. Requires both order_id and the email used for the order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id returned by create_order |
| string | yes | The email used for the order |
After payment: link to the order page with the QR code and step-by-step eSIM install instructions for iPhone and Android. Requires order_id and email.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id returned by create_order |
| string | yes | The email used for the order |
- 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 SOS or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_destinations | no tags | |
| list_plans | no tags | |
| compare_prices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create_order | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| order_status | no tags | |
| install_instructions | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 1.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish eSIM SOS can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.