# esimker eSIM store (remote · esimker.com)

Prepaid travel data eSIMs: checkout links for people, autonomous purchases from a prepaid wallet.

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

## Components

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

## Channel facts

- Endpoint: `https://esimker.com/api/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-09-26.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1821 tokens (~151/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the esimker eSIM store MCP server?

esimker eSIM store is a hosted endpoint at https://esimker.com/api/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-esimker-esim 'https://esimker.com/api/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-esimker-esim": {
      "type": "http",
      "url": "https://esimker.com/api/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-09-26 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 69, 0)

- [security] Tool “search_destinations” rewrote its description, which is the text the model reads

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

## MCP tools (12)

### `search_destinations` (~97 tokens)

Destinations on sale. `query` matches the name in any of 18 languages, the
        slug or the ISO code; empty lists everything. Each item: dest_code, slug, name,
        min_retail (USD, the cheapest fixed plan), unlimited_from (USD per day of a
        Daily Unlimited pass, or null), plan_count. Continue with get_plans(slug).

Input parameters:

- `query` (string)

Output parameters:

- `result` (array)

### `get_plans` (~90 tokens)

The plans of one destination (slug from search_destinations). Each plan: id
        (the plan_id for an order), name, gb, days, retail (USD; per day when
        daily_unlimited is true), daily_unlimited, location_codes (the countries it
        covers), networks, speed, supports_topup. Also the published rating.

Input parameters:

- `slug` (string, required)

### `get_payment_methods` (~86 tokens)

Checkout methods open right now: "crypto" (a hosted invoice: BTC, ETH, TRX,
        USDT), "card", and "wallet" (a prepaid balance, see create_wallet).

        `gateways` names the providers behind each method; a checkout that does not
        ask for one by name goes to the first, which is what these tools do.

### `create_checkout` (~216 tokens)

Create an order for a person to pay. Returns token, checkout_url (the
        gateway's page: hand it to the person) and order_url (the order page in `lang`,
        with the QR code once paid: show it to the buyer only, the token is a secret).
        Confirm the plan and the price first: every call creates a new unpaid order,
        so do not retry while a checkout is open. `email` (optional) also gets the eSIM
        by mail. `period_num` (1–365) only for daily_unlimited plans. `topup_iccid`
        with a plan_id from list_topups tops up an existing eSIM. A 403 means the
        caller's jurisdiction is embargoed. To pay from a wallet use purchase_esim.

Input parameters:

- `email`
- `lang` (string)
- `payment_method` (string)
- `period_num`
- `plan_id` (integer, required)
- `topup_iccid`

### `get_order` (~99 tokens)

An order by its token. status goes pending (unpaid) → paid → provisioning →
        ready; also expired, underpaid, failed_provisioning, gift_waiting. When ready,
        esim.activation_code is the LPA string (render it as a QR code), with iccid,
        smdp and matching_id. After payment poll every ~10 s; delivery usually takes
        under a minute.

Input parameters:

- `token` (string, required)

### `list_topups` (~80 tokens)

Top-up plans that fit an eSIM we issued: plan_id, name, gb, days, retail.
        Order one with create_checkout(plan_id, topup_iccid=iccid) or, from a wallet,
        purchase_esim(plan_id, client_ref, topup_iccid=iccid).

Input parameters:

- `iccid` (string, required)

Output parameters:

- `result` (array)

### `get_usage` (~27 tokens)

Remaining data and status of an eSIM we issued.

Input parameters:

- `iccid` (string, required)

### `create_wallet` (~153 tokens)

Mint a prepaid wallet with no account behind it and get its secret ONCE:
        `code` (32 hex characters) and the same secret as a 12-word `phrase`. Save the
        code before doing anything else and send it as `Authorization: Bearer <code>`
        on every wallet call; there is no recovery and no identity to prove. The
        balance is spent on eSIMs (retail price, cashback on every purchase) and never
        paid back out. accept_terms must be true (https://esimker.com/terms). Then
        create_deposit to fund it. Rate-limited and geo-blocked like checkout.

Input parameters:

- `accept_terms` (boolean, required)

### `get_wallet` (~89 tokens)

The wallet behind the code: ref (a public handle for support), balance_usd,
        cashback_percent, the deposit rules that apply to it now (min_usd, max_usd,
        first, bonus tiers), the last 50 transactions, orders (with their tokens — the
        wallet is where a buyer's order links are kept) and deposits. Needs the wallet
        code.

### `create_deposit` (~233 tokens)

Open a top-up of the wallet and get what is needed to pay it. Floors: $10 for a wallet's first deposit, $1 after that; cap $1000 per deposit. Crypto deposits earn a bonus (+2% from $25, +3% from $50, +5% from $100, capped at $25); every purchase returns 3% cashback. With payment_method "crypto" pass a currency from: BTC, ETH, TRX, USDTTRC, USDTETH, USDTBSC — the answer then carries `pay`: the address, the exact amount in the coin (network fee included) and expires_at (about 15 minutes; after that open a new deposit). Send exactly `pay.amount` to `pay.address` on `pay.network`, then poll get_deposit(token) until status is paid. checkout_url is the hosted pay page for a person; card deposits have only that. Needs the wallet code.

Input parameters:

- `amount_usd` (required)
- `currency`
- `lang` (string)
- `payment_method` (string)

### `get_deposit` (~76 tokens)

One deposit of the wallet by its token: status pending → paid (credited,
        bonus included) | underpaid (nothing credited yet, the rest can still arrive) |
        expired. Poll every ~30 s after sending; crypto needs the network's
        confirmations. Needs the wallet code.

Input parameters:

- `token` (string, required)

### `purchase_esim` (~236 tokens)

Charge the wallet and issue an eSIM, no checkout. `client_ref` (1–64 chars) is your own reference for this purchase and makes the call idempotent: a retry with the same value returns the existing order without a second charge, so reuse it after a timeout and never invent a new one for the same purchase. `period_num` (1–365, default 7) only for daily_unlimited plans; the charge is price × days. `topup_iccid` with a plan_id from list_topups tops up an eSIM. Returns the order (status paid) with order_url; poll get_order(token) for ready and the activation code. A 402 is a short balance: create_deposit first. A wallet pays for at most 50 orders in 24 hours (429 beyond that; a retry answered from client_ref does not count). Needs the wallet code.

Input parameters:

- `client_ref` (string, required)
- `email`
- `lang` (string)
- `period_num`
- `plan_id` (integer, required)
- `topup_iccid`

## Diagnostics

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

## Score history

- 2026-09-26: 74
- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 72
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 67
- 2026-09-11: 67
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 65
- 2026-09-07: 65
- 2026-09-06: 65
- 2026-09-05: 64
- 2026-09-04: 64

## Common questions

### What is the esimker eSIM store MCP server?

esimker eSIM store is an MCP server listed in the public MCP registry as com.esimker/esim. Prepaid travel data eSIMs: checkout links for people, autonomous purchases from a prepaid wallet. This page covers its hosted endpoint (https://esimker.com/api/mcp).

### Is the esimker eSIM store MCP server safe to use?

esimker eSIM store scores 74 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 esimker eSIM store MCP server expose?

esimker eSIM store exposes 12 tools: search_destinations, get_plans, get_payment_methods, create_checkout, get_order, and 7 more. Their descriptions and schemas cost roughly 1,482 tokens of context every time the server is loaded.

### Does the esimker eSIM store MCP server require authentication?

No. We connected to esimker eSIM store without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the esimker eSIM store MCP server still maintained?

esimker eSIM store is still listed as active in the MCP registry. We last reached this channel on 26 September 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://esimker.com/api/mcp
- Website: https://esimker.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-esimker-esim/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-esimker-esim/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-esimker-esim/api-mcp