# ChoEsim Travel eSIM (remote · choesim.com)

Search prepaid travel eSIM data plans for 200+ countries, with prices and one-step cart links.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://choesim.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 416 tokens (~138/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ChoEsim Travel eSIM MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-choesim-travel-esim": {
      "type": "http",
      "url": "https://choesim.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-11-20 (score 74, +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-11-18 (score 73, +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-11-16 (score 72, 0)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “search_plans” reworded the description of “destination”
- [cosmetic] “search_plans” reworded the description of “min_days”

### 2026-11-15 (score 72)

First indexed and scored.

## MCP tools (3)

### `search_plans` (~229 tokens)

Search travel eSIM plans

Find purchasable eSIM data plans for a destination, cheapest first. Returns price in USD, data, validity, coverage, plan page URL and a cart URL that opens choesim.com with the plan in the cart.

Input parameters:

- `destination` (string, required): Country name in English (e.g. "Japan") or a common local name (e.g. "Nhật Bản", "Japón", "日本"), or ISO 3166-1 alpha-2 code (e.g. "JP"). A region word such as "Europe", "Asia" or "Global" matches regi…
- `include_regional` (boolean): Also list multi-country plans that cover the destination (default true).
- `max_results` (integer): Default 10.
- `min_days` (integer): Trip length in days: the plan must last at least this long. Pay-per-day plans are listed for trips of up to 30 days.
- `min_gb` (number): Smallest total data in GB (for pay-per-day plans: data per day times min_days).

### `get_plan` (~54 tokens)

Get one eSIM plan

Details of one plan by id (from search_plans): price, data, validity, coverage, network speed, when validity starts, fair-use note, plan page and cart URL.

Input parameters:

- `id` (string, required): Plan id

### `get_policies` (~39 tokens)

ChoEsim policies

Facts that apply to every ChoEsim plan: device requirements, data-only, delivery, refund rule, support contact, payment methods, with links.

## Diagnostics

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

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 72

## Common questions

### What is the ChoEsim Travel eSIM MCP server?

ChoEsim Travel eSIM is an MCP server listed in the public MCP registry as com.choesim/travel-esim. Search prepaid travel eSIM data plans for 200+ countries, with prices and one-step cart links. This page covers its hosted endpoint (https://choesim.com/api/mcp).

### Is the ChoEsim Travel eSIM MCP server safe to use?

ChoEsim Travel eSIM 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 ChoEsim Travel eSIM MCP server expose?

ChoEsim Travel eSIM exposes 3 tools: search_plans, get_plan, get_policies. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.

### Does the ChoEsim Travel eSIM MCP server require authentication?

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

### Is the ChoEsim Travel eSIM MCP server still maintained?

ChoEsim Travel eSIM is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ChoEsim Travel eSIM MCP server?

VerifyMCP ran 13 checks on ChoEsim Travel eSIM, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://choesim.com/api/mcp
- Website: https://choesim.com/llms-full.txt
- Changelog RSS feed: https://verifymcp.io/servers/com-choesim-travel-esim/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-choesim-travel-esim/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-choesim-travel-esim/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-choesim-travel-esim/api-mcp
