Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Cypher eSIM 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.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Buy no-KYC travel eSIMs and eSIMs with a real phone number in 180+ countries, paid in crypto.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cypher-esim-mcp https://cypheresim.com/mcp
# 2 — ask your agent for something these tools do
# search_destinations, list_plans, get_plan and 6 more
Cypher eSIM costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CYAll 1 server
cypheresim1 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 cypher-esim-mcp https://cypheresim.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
9 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 country, region or "world" destination by name or ISO code. Returns destination codes for list_plans (country: ISO2 like "JP"; region: like "R-EUROPE"; world: "WORLD"), starting prices in USD, and how many data and phone-number plans exist. An empty query lists all destinations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Country or region name, or ISO2 code, e.g. "Japan", "JP", "Europe" |
| limit | integer | no | Max results, default 20 |
List purchasable plans for a destination, cheapest first. type "data" = data-only eSIM: validity starts on first connection at the destination. type "number" = eSIM with a phone number, calls and SMS: validity starts at installation, so install it just before use; Europe plans give a French +33 number; the UK number plan must be installed only after arrival in the UK. For a country without its own
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Destination code from search_destinations, or a country ISO2 code |
| type | string | no | "data" (default) or "number" (plan with a phone number) |
| include_regional | boolean | no | For a country: also return regional/world plans covering it |
Full details of one plan: all covered countries, data, days, phone number (if any), install rules, when validity starts, and notes. Read the notes to the person before create_order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | plan_id from list_plans |
Coins and networks accepted for payment. Pass coin and network to create_order. Sending on a different network loses the funds.
No parameter schema on file.
Create a crypto invoice for one new eSIM. Before calling, confirm the plan with the person and tell them when validity starts and the plan notes (number plans: validity starts at installation; Europe number is French +33; UK number plan: install only after arrival). Returns order_id, order_token, the exact amount and the address. The person must send exactly that amount on that network before expi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | plan_id from list_plans |
| coin | string | yes | Coin code from list_payment_coins, e.g. "USDT", "BTC", "XMR" |
| network | string | no | Network from list_payment_coins, e.g. "tron", "solana". Required for USDT (several networks). |
| ref | string | no | Optional partner/referral code |
| quantity | integer | no | Resellers with an API key only: number of identical eSIMs on one invoice (1-50). Omit otherwise. |
| client_ref | string | no | Resellers only: your own order reference, returned as is. |
Order status: pending (waiting for payment), paid (issuing), delivered, expired, failed. When delivered, returns for each eSIM: QR code (also as an image), LPA activation code, ICCID, and one-tap iOS/Android install links. Call at most once every 5 seconds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id returned by create_order |
| order_token | string | yes | order_token returned by create_order |
Cancel an unpaid order the person decided not to pay. Do not cancel after the payment was sent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id returned by create_order |
| order_token | string | yes | order_token returned by create_order |
Check whether an installed Cypher eSIM can be topped up and list the plans that can be added to it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| iccid | string | yes | ICCID of the installed eSIM (18-22 digits, printed in the eSIM settings) |
Create a crypto invoice that adds a data plan to an existing eSIM (no new QR, nothing to install). plan_id must come from list_topups for this ICCID. Payment and polling work exactly like create_order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| iccid | string | yes | ICCID of the installed eSIM (18-22 digits, printed in the eSIM settings) |
| plan_id | string | yes | plan_id from list_plans |
| coin | string | yes | Coin code from list_payment_coins, e.g. "USDT", "BTC", "XMR" |
| network | string | no | Network from list_payment_coins, e.g. "tron", "solana". Required for USDT (several networks). |
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 Cypher eSIM 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: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 24 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestcae47edf1fc36b480601a3c768eb1c11c5df914f090aed152931dec60b1f444b
Score vectorthreat 100 → client 93
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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 | |
| get_plan | no tags | |
| list_payment_coins | no tags | |
| create_order | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_order | no tags | |
| cancel_order | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_topups | no tags | |
| create_topup | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestcae47edf1fc36b48
Scanned2026-10-24
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.
1.0.0
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 Cypher eSIM 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.