# Bloomy eSIM (remote · bloomyesim.com)

Recommend the right travel eSIM for any trip (200+ countries) and hand the traveler a checkout link.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `bloomyesim.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-bloomyesim-esim/wp-json-bloomy-v1-mcp.md), [page](https://verifymcp.io/servers/com-bloomyesim-esim/wp-json-bloomy-v1-mcp)

## Channel facts

- Endpoint: `https://bloomyesim.com/wp-json/bloomy/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-27.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1059 tokens (~132/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Bloomy eSIM MCP server?

Bloomy eSIM is a hosted endpoint at https://bloomyesim.com/wp-json/bloomy/v1/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-bloomyesim-esim 'https://bloomyesim.com/wp-json/bloomy/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-bloomyesim-esim": {
      "url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-bloomyesim-esim": {
      "type": "http",
      "url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-bloomyesim-esim]
url = "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-bloomyesim-esim --url 'https://bloomyesim.com/wp-json/bloomy/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-bloomyesim-esim:
    url: "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-bloomyesim-esim": {
      "Transport": "http",
      "Url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-bloomyesim-esim -t streamable-http -u 'https://bloomyesim.com/wp-json/bloomy/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-bloomyesim-esim": {
      "type": "http",
      "url": "https://bloomyesim.com/wp-json/bloomy/v1/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 72, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.2.0 → 1.3.0

### 2026-09-25 (score 71)

First indexed and scored.

## MCP tools (7)

### `recommend_plan` (~364 tokens)

Recommend the best eSIM for a trip

Best first call. Give the destination (or all destinations of a multi-country trip) and trip length, plus how the traveler uses data if known. Returns up to 3 options with a reason each: best_fit (cheapest that covers the estimated need), budget (cheaper, below the estimate) and roomier (next size up), each with a link straight to checkout confirmation. If the traveler pastes an itinerary or flight details, extract every country visited and the total days and pass them as destinations + days.

Input parameters:

- `activities` (array): Specific uses named by the traveler (e.g. hotspot_light for tethering, video_call, video). Overrides usage. Same categories as bloomyesim.com/data-calculator.
- `days` (integer, required): Trip length in days (total for a multi-country trip).
- `destination` (string): Country name in any of en/ja/zh/ko/es/fr (e.g. "Turkey", "トルコ", "Türkiye") or ISO 3166-1 alpha-2 code ("TR"). For one country.
- `destinations` (array): For a trip through several countries: every country visited (names or ISO codes). One eSIM covering all of them is searched. Use instead of destination.
- `lang` (string): Language for names and for the purchase page. Default en.
- `min_gb` (number): Use this instead of usage/activities when the traveler already knows the GB they want.
- `usage` (string): light = maps and messaging, normal = maps, messaging, web and social (default), heavy = plus video streaming. Use activities instead when the traveler names specific uses.
- `wifi` (string): How often hotel/cafe Wi-Fi is used. Default sometimes.

### `search_plans` (~157 tokens)

Search eSIM plans for a destination

List plans for a destination, cheapest first, single-country plans before multi-country ones. Filter by trip length, minimum GB, and plan type.

Input parameters:

- `destination` (string, required): Country name (any supported language) or ISO alpha-2 code.
- `lang` (string): Language for names and for the purchase page. Default en.
- `limit` (integer): Default 8.
- `min_days` (integer): Trip length. Fixed-GB plans shorter than this are skipped; daily plans get the trip total.
- `min_gb` (number): Minimum GB (daily allowance for daily plans).
- `plan_type` (string): "data" = fixed GB for the whole period, "unlimited" = priced per day.

### `estimate_data` (~61 tokens)

Estimate how much data a trip needs

Same formula as bloomyesim.com/data-calculator: daily MB per activity x days x Wi-Fi factor x 1.15 safety buffer, rounded up.

Input parameters:

- `activities` (array, required)
- `days` (integer, required)
- `wifi` (string)

### `list_destinations` (~73 tokens)

List destinations Bloomy covers

Countries with a dedicated plan, with ISO code, localized name, number of plans and the lowest price. Use query to filter.

Input parameters:

- `lang` (string): Language for names and for the purchase page. Default en.
- `query` (string): Part of a country name or code. Omit to list all.

### `get_plan` (~78 tokens)

Get one plan

Details of one plan: data, validity, network, 5G, top-up, carriers, price and checkout link.

Input parameters:

- `days` (integer): Trip length (sets the day count and total for daily plans).
- `lang` (string): Language for names and for the purchase page. Default en.
- `plan_id` (integer, required)

### `get_purchase_link` (~86 tokens)

Get the checkout link for a plan

Link straight to the final confirmation screen for this plan. The traveler pays there themselves; this tool never takes payment. The QR code is emailed and shown in My Page right after payment.

Input parameters:

- `days` (integer): Trip length (needed for daily plans).
- `lang` (string): Language for names and for the purchase page. Default en.
- `plan_id` (integer, required)

### `get_setup_guide` (~65 tokens)

How to install and start using the eSIM

Short, accurate setup steps (iPhone or Android), what to check before buying, and links to the full guide, the device checker and troubleshooting.

Input parameters:

- `device` (string)
- `lang` (string): Language for names and for the purchase page. Default en.

## Diagnostics

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

## Score history

- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71

## Common questions

### What is the Bloomy eSIM MCP server?

Bloomy eSIM is an MCP server listed in the public MCP registry as com.bloomyesim/esim. Recommend the right travel eSIM for any trip (200+ countries) and hand the traveler a checkout link. This page covers its hosted endpoint (https://bloomyesim.com/wp-json/bloomy/v1/mcp).

### Is the Bloomy eSIM MCP server safe to use?

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

Bloomy eSIM exposes 7 tools: recommend_plan, search_plans, estimate_data, list_destinations, get_plan, and 2 more. Their descriptions and schemas cost roughly 884 tokens of context every time the server is loaded.

### Does the Bloomy eSIM MCP server require authentication?

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

### Is the Bloomy eSIM MCP server still maintained?

Bloomy eSIM is still listed as active in the MCP registry. We last reached this channel on 27 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://bloomyesim.com/wp-json/bloomy/v1/mcp
- Website: https://bloomyesim.com/en/ai-agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-bloomyesim-esim/wp-json-bloomy-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bloomyesim-esim/wp-json-bloomy-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-bloomyesim-esim/wp-json-bloomy-v1-mcp