Bloomy eSIM
REMOTE · BLOOMYESIM.COM · SCANNED SEP 27
Recommend the right travel eSIM for any trip (200+ countries) and hand the traveler a checkout link.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
- Supports UI / widget rendering.Pass
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.
remote · bloomyesim.com
claude mcp add --transport http com-bloomyesim-esim 'https://bloomyesim.com/wp-json/bloomy/v1/mcp'
{
"mcpServers": {
"com-bloomyesim-esim": {
"url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
}
}
} {
"servers": {
"com-bloomyesim-esim": {
"type": "http",
"url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
}
}
} [mcp_servers.com-bloomyesim-esim] url = "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-bloomyesim-esim": {
"type": "remote",
"url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-bloomyesim-esim --url 'https://bloomyesim.com/wp-json/bloomy/v1/mcp' --transport streamable-http
mcp_servers:
com-bloomyesim-esim:
url: "https://bloomyesim.com/wp-json/bloomy/v1/mcp" {
"McpServers": {
"com-bloomyesim-esim": {
"Transport": "http",
"Url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
}
}
} assistant mcp add com-bloomyesim-esim -t streamable-http -u 'https://bloomyesim.com/wp-json/bloomy/v1/mcp'
{
"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.
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.
- 26 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.3.0 functional
- 25 Sept 26 71
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 27 Sept 2026 · Probed https://bloomyesim.com/wp-json/bloomy/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.bloomyesim.com | CN=YR1,O=Let's Encrypt,C=US | 9 Aug 2026 | 7 Nov 2026 | RSA 2048 | SHA256-RSA | 66b0875a21f5fae1097746da19a25272062 |
| SANs: bloomyesim.com, www.bloomyesim.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 bloomyesim.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bloomyesim.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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bloomyesim.com/wp-json/bloomy/v1/mcp | Verified | 200 | |
| http (plaintext) | http://bloomyesim.com/wp-json/bloomy/v1/mcp | HTTPS enforced | 301 | https://bloomyesim.com/wp-json/bloomy/v1/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 →
estimate_data Estimate how much data a trip needs ~61
Same formula as bloomyesim.com/data-calculator: daily MB per activity x days x Wi-Fi factor x 1.15 safety buffer, rounded up.
| Name | Type | Req | Description |
|---|---|---|---|
| activities | array | yes | – |
| days | integer | yes | – |
| wifi | string | – | – |
No output schema declared.
No examples provided.
get_plan Get one plan ~78
Details of one plan: data, validity, network, 5G, top-up, carriers, price and checkout link.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
get_purchase_link Get the checkout link for a plan ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Trip length (needed for daily plans). |
| lang | string | – | Language for names and for the purchase page. Default en. |
| plan_id | integer | yes | – |
No output schema declared.
No examples provided.
get_setup_guide How to install and start using the eSIM ~65
Short, accurate setup steps (iPhone or Android), what to check before buying, and links to the full guide, the device checker and troubleshooting.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | – |
| lang | string | – | Language for names and for the purchase page. Default en. |
No output schema declared.
No examples provided.
list_destinations List destinations Bloomy covers ~73
Countries with a dedicated plan, with ISO code, localized name, number of plans and the lowest price. Use query to filter.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
recommend_plan Recommend the best eSIM for a trip ~364
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
search_plans Search eSIM plans for a destination ~157
List plans for a destination, cheapest first, single-country plans before multi-country ones. Filter by trip length, minimum GB, and plan type.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | 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. |
No output schema declared.
No examples provided.
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.