Cypher eSIM
REMOTE · CYPHERESIM.COM
Buy no-KYC travel eSIMs and eSIMs with a real phone number in 180+ countries, paid in crypto.
Available components
Last scanned (21 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category IoT and Hardware
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1198 tokens (~133/item across 9 items; 9 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 66
First indexed and scored.
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 4 Nov 2026 · Probed https://cypheresim.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cypheresim.com | CN=YR1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 6448405e3b221b60bd8d39ee32bede13a43 |
| SANs: cypheresim.com, www.cypheresim.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cypheresim.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cypheresim.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cypheresim.com/mcp | Verified | 200 | |
| http (plaintext) | http://cypheresim.com/mcp | HTTPS enforced | 301 | https://cypheresim.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 order ~56
Cancel an unpaid order the person decided not to pay. Do not cancel after the payment was sent.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id returned by create_order |
| order_token | string | yes | order_token returned by create_order |
No output schema declared.
No examples provided.
create_order Create order ~248
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 expires_at. Then poll get_order. Unpaid invoices per client are limited; cancel unused ones with cancel_order.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ref | string | – | Resellers only: your own order reference, returned as is. |
| coin | string | yes | Coin code from list_payment_coins, e.g. "USDT", "BTC", "XMR" |
| network | string | – | Network from list_payment_coins, e.g. "tron", "solana". Required for USDT (several networks). |
| plan_id | string | yes | plan_id from list_plans |
| quantity | integer | – | Resellers with an API key only: number of identical eSIMs on one invoice (1-50). Omit otherwise. |
| ref | string | – | Optional partner/referral code |
No output schema declared.
No examples provided.
create_topup Create top-up ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Coin code from list_payment_coins, e.g. "USDT", "BTC", "XMR" |
| iccid | string | yes | ICCID of the installed eSIM (18-22 digits, printed in the eSIM settings) |
| network | string | – | Network from list_payment_coins, e.g. "tron", "solana". Required for USDT (several networks). |
| plan_id | string | yes | plan_id from list_plans |
No output schema declared.
No examples provided.
get_order Get order ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | order_id returned by create_order |
| order_token | string | yes | order_token returned by create_order |
No output schema declared.
No examples provided.
get_plan Get plan ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | plan_id from list_plans |
No output schema declared.
No examples provided.
list_payment_coins List payment coins ~34
Coins and networks accepted for payment. Pass coin and network to create_order. Sending on a different network loses the funds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_plans List plans ~187
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 plans, regional and world plans that cover it are returned. Prices are final USD prices; the crypto amount is set at create_order.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination code from search_destinations, or a country ISO2 code |
| include_regional | boolean | – | For a country: also return regional/world plans covering it |
| type | string | – | "data" (default) or "number" (plan with a phone number) |
No output schema declared.
No examples provided.
list_topups List top-ups ~59
Check whether an installed Cypher eSIM can be topped up and list the plans that can be added to it.
| Name | Type | Req | Description |
|---|---|---|---|
| iccid | string | yes | ICCID of the installed eSIM (18-22 digits, printed in the eSIM settings) |
No output schema declared.
No examples provided.
search_destinations Search destinations ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, default 20 |
| query | string | – | Country or region name, or ISO2 code, e.g. "Japan", "JP", "Europe" |
No output schema declared.
No examples provided.
How do I install the Cypher eSIM MCP server?
Cypher eSIM is a hosted endpoint at https://cypheresim.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 · cypheresim.com
claude mcp add --transport http com-cypheresim-esim 'https://cypheresim.com/mcp'
What is the Cypher eSIM MCP server?
Cypher eSIM is an MCP server listed in the public MCP registry as com.cypheresim/esim. Buy no-KYC travel eSIMs and eSIMs with a real phone number in 180+ countries, paid in crypto. This page covers its hosted endpoint (https://cypheresim.com/mcp).
Is the Cypher eSIM MCP server safe to use?
Cypher eSIM scores 72 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 Cypher eSIM MCP server expose?
Cypher eSIM exposes 9 tools: search_destinations, list_plans, get_plan, list_payment_coins, create_order, and 4 more. Their descriptions and schemas cost roughly 1,021 tokens of context every time the server is loaded.
Does the Cypher eSIM MCP server require authentication?
No. We connected to Cypher eSIM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cypher eSIM MCP server still maintained?
Cypher eSIM is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.