# Cypher eSIM (remote · cypheresim.com)

Buy no-KYC travel eSIMs and eSIMs with a real phone number in 180+ countries, paid in crypto.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cypheresim.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-cypheresim-esim/cypheresim.md), [page](https://verifymcp.io/servers/com-cypheresim-esim/cypheresim)

## Channel facts

- Endpoint: `https://cypheresim.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_order).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-cypheresim-esim 'https://cypheresim.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cypheresim-esim": {
      "url": "https://cypheresim.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cypheresim-esim": {
      "type": "http",
      "url": "https://cypheresim.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cypheresim-esim]
url = "https://cypheresim.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cypheresim-esim": {
      "type": "remote",
      "url": "https://cypheresim.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cypheresim-esim --url 'https://cypheresim.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cypheresim-esim:
    url: "https://cypheresim.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cypheresim-esim": {
      "Transport": "http",
      "Url": "https://cypheresim.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cypheresim-esim -t streamable-http -u 'https://cypheresim.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cypheresim-esim": {
      "type": "http",
      "url": "https://cypheresim.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 72, +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.

### 2026-11-01 (score 71, +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.

### 2026-10-30 (score 70, +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.

### 2026-10-28 (score 69, +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.

### 2026-10-26 (score 68, +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.

### 2026-10-24 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 66)

First indexed and scored.

## MCP tools (9)

### `search_destinations` (~119 tokens)

Search destinations

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.

Input parameters:

- `limit` (integer): Max results, default 20
- `query` (string): Country or region name, or ISO2 code, e.g. "Japan", "JP", "Europe"

### `list_plans` (~187 tokens)

List plans

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.

Input parameters:

- `destination` (string, required): 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)

### `get_plan` (~62 tokens)

Get plan

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.

Input parameters:

- `plan_id` (string, required): plan_id from list_plans

### `list_payment_coins` (~34 tokens)

List payment coins

Coins and networks accepted for payment. Pass coin and network to create_order. Sending on a different network loses the funds.

### `create_order` (~248 tokens)

Create order

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.

Input parameters:

- `client_ref` (string): Resellers only: your own order reference, returned as is.
- `coin` (string, required): 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, required): 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

### `get_order` (~101 tokens)

Get order

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.

Input parameters:

- `order_id` (string, required): order_id returned by create_order
- `order_token` (string, required): order_token returned by create_order

### `cancel_order` (~56 tokens)

Cancel order

Cancel an unpaid order the person decided not to pay. Do not cancel after the payment was sent.

Input parameters:

- `order_id` (string, required): order_id returned by create_order
- `order_token` (string, required): order_token returned by create_order

### `list_topups` (~59 tokens)

List top-ups

Check whether an installed Cypher eSIM can be topped up and list the plans that can be added to it.

Input parameters:

- `iccid` (string, required): ICCID of the installed eSIM (18-22 digits, printed in the eSIM settings)

### `create_topup` (~155 tokens)

Create top-up

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.

Input parameters:

- `coin` (string, required): Coin code from list_payment_coins, e.g. "USDT", "BTC", "XMR"
- `iccid` (string, required): 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, required): plan_id from list_plans

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cypheresim-esim/cypheresim#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 66

## Common questions

### 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cypheresim.com/mcp
- Website: https://cypheresim.com/for-ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-cypheresim-esim/cypheresim.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cypheresim-esim/cypheresim.json
- HTML version of this page: https://verifymcp.io/servers/com-cypheresim-esim/cypheresim