Bloomy eSIM
REMOTE · BLOOMYESIM.COM
Travel data eSIMs, 200+ countries: plan picks from destination + days, live prices, checkout link.
Available components
Last scanned (21 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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. 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. 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 Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2153 tokens (~269/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “estimate_data” rewrote its description, which is the text the model reads security
- Tool “get_plan” rewrote its description, which is the text the model reads security
- Tool “get_purchase_link” rewrote its description, which is the text the model reads security
- Tool “get_setup_guide” rewrote its description, which is the text the model reads security
- Tool “list_destinations” rewrote its description, which is the text the model reads security
- Tool “recommend_plan” rewrote its description, which is the text the model reads security
- Tool “search_plans” rewrote its description, which is the text the model reads security
- Schema quality: 154 → 269 ▼ functional
- Tool coverage: 78% → 100% ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.3.0 → 1.4.0 functional
- “estimate_data” reworded the description of “activities” cosmetic
- “estimate_data” reworded the description of “days” cosmetic
- “estimate_data” reworded the description of “wifi” cosmetic
- “get_plan” reworded the description of “days” cosmetic
- “get_plan” reworded the description of “lang” cosmetic
- “get_plan” reworded the description of “plan_id” cosmetic
- “get_purchase_link” reworded the description of “days” cosmetic
- “get_purchase_link” reworded the description of “lang” cosmetic
- “get_purchase_link” reworded the description of “plan_id” cosmetic
- “get_setup_guide” reworded the description of “device” cosmetic
- “get_setup_guide” reworded the description of “lang” cosmetic
- “list_destinations” reworded the description of “lang” cosmetic
- “list_destinations” reworded the description of “query” cosmetic
- “recommend_plan” reworded the description of “activities” cosmetic
- “recommend_plan” reworded the description of “days” cosmetic
- “recommend_plan” reworded the description of “destination” cosmetic
- “recommend_plan” reworded the description of “destinations” cosmetic
- “recommend_plan” reworded the description of “lang” cosmetic
- “recommend_plan” reworded the description of “min_gb” cosmetic
- “recommend_plan” reworded the description of “usage” cosmetic
- “recommend_plan” reworded the description of “wifi” cosmetic
- “search_plans” reworded the description of “destination” cosmetic
- “search_plans” reworded the description of “lang” cosmetic
- “search_plans” reworded the description of “limit” cosmetic
- “search_plans” reworded the description of “min_days” cosmetic
- “search_plans” reworded the description of “min_gb” cosmetic
- “search_plans” reworded the description of “plan_type” cosmetic
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 13 Oct 26 0
- Tool “list_destinations” rewrote its description, which is the text the model reads security
- Tool “recommend_plan” rewrote its description, which is the text the model reads security
- Schema quality: 132 → 154 ▼ functional
- “get_plan” reworded the description of “lang” cosmetic
- “get_purchase_link” reworded the description of “lang” cosmetic
- “get_setup_guide” reworded the description of “lang” cosmetic
- “list_destinations” reworded the description of “lang” cosmetic
- “recommend_plan” reworded the description of “destinations” cosmetic
- “recommend_plan” reworded the description of “lang” cosmetic
- “recommend_plan” reworded the description of “min_gb” cosmetic
- “recommend_plan” reworded the description of “usage” cosmetic
- “search_plans” reworded the description of “destination” cosmetic
- “search_plans” reworded the description of “lang” cosmetic
- “search_plans” reworded the description of “plan_type” cosmetic
- Tool “estimate_data” changed its title: Estimate how much data a trip needs → Estimate data needed cosmetic
- Tool “get_plan” changed its title: Get one plan → Get plan details cosmetic
- Tool “get_purchase_link” changed its title: Get the checkout link for a plan → Get checkout link cosmetic
- Tool “get_setup_guide” changed its title: How to install and start using the eSIM → Get setup guide cosmetic
- Tool “list_destinations” changed its title: List destinations Bloomy covers → List destinations cosmetic
- Tool “recommend_plan” changed its title: Recommend the best eSIM for a trip → Recommend a plan cosmetic
- Tool “search_plans” changed its title: Search eSIM plans for a destination → Search plans cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.3.0 functional
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 21 Nov 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=YR2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 6ce3c75fb6d8e5c9ae0a3a8078e7e4ca601 |
| SANs: bloomyesim.com, www.bloomyesim.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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. | DS published | 19718 | 13 | Verified |
| bloomyesim.com. | No DS | 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 data needed ~164
Use when the traveler asks how much data they need, without choosing a plan yet. Returns estimated_gb for the trip, estimated_daily_gb and recommended_min_gb. 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 | Required. What mobile data will be used for, e.g. ["maps", "messaging", "video"]. hotspot_light / hotspot_heavy mean sharing the connection with another device. |
| days | integer | yes | Required. Trip length in days, integer 1 to 180. |
| wifi | string | – | How often hotel or cafe Wi-Fi replaces mobile data: rarely, sometimes (default) or often. |
No output schema declared.
No examples provided.
get_plan Get plan details ~204
Use for questions about one plan returned by another tool. Details of one Bloomy eSIM plan by plan_id: data, validity, when validity starts, network (4G/5G) and carriers per country, top-up support, price_jpy, price_usd, price_as_of and the checkout link.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Trip length in days. For daily plans it sets the number of days and the total price; ignored for fixed-GB plans. |
| lang | string | – | Language of country names, reasons and of the checkout page the link opens: en, ja, zh-cn, zh-tw, ko, es or fr. Default en. The language never changes which plan or what price is returned: every plan… |
| plan_id | integer | yes | Required. The plan_id from recommend_plan or search_plans, e.g. 14085. |
No output schema declared.
No examples provided.
get_purchase_link Get checkout link ~211
Use when the traveler has chosen a plan and wants to buy it. Returns a link straight to the checkout confirmation screen with the plan and days filled in. The traveler pays there themselves (no account or app needed, just an email address); this tool never takes payment. The QR code and one-tap install link are emailed and shown in My Page right after payment.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Trip length in days. Needed for daily plans (sets how many days are bought); ignored for fixed-GB plans. |
| lang | string | – | Language of country names, reasons and of the checkout page the link opens: en, ja, zh-cn, zh-tw, ko, es or fr. Default en. The language never changes which plan or what price is returned: every plan… |
| plan_id | integer | yes | Required. The plan_id of the chosen plan, from recommend_plan or search_plans. |
No output schema declared.
No examples provided.
get_setup_guide Get setup guide ~159
Use for questions about compatibility, installing or connecting. Short setup steps for iPhone or Android (no app to download: install from the QR code or one-tap link in the phone settings), what to check before buying, and links to the full guide, the device checker and troubleshooting.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | The traveler's phone: iphone or android. Default iphone. |
| lang | string | – | Language of country names, reasons and of the checkout page the link opens: en, ja, zh-cn, zh-tw, ko, es or fr. Default en. The language never changes which plan or what price is returned: every plan… |
No output schema declared.
No examples provided.
list_destinations List destinations ~182
Use to check whether Bloomy eSIM has plans for a place, or to list all destinations. Returns countries with a dedicated plan: ISO code, localized name, number of plans and the lowest price (from_jpy, from_usd). Many more countries are covered by regional plans (200+ countries and regions in total).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of country names, reasons and of the checkout page the link opens: en, ja, zh-cn, zh-tw, ko, es or fr. Default en. The language never changes which plan or what price is returned: every plan… |
| query | string | – | Part of a country name or ISO code to filter by, e.g. "tur" or "TR". Omit to list all. |
No output schema declared.
No examples provided.
recommend_plan Recommend a plan ~613
Use when a traveler asks which eSIM to get for a trip. Input: destination (or every country of a multi-country trip in destinations), trip length in days, and how they use data if known. Estimates the GB the trip needs (need_gb, same formula as estimate_data), then returns up to 3 Bloomy eSIM plans with a reason each: best_fit (lowest price in our catalog that covers the estimate), budget (cheaper, below the estimate) and roomier (next size up). A multi-country trip is matched to one regional plan that covers every country. Each option has data, validity, networks (4G/5G per carrier), top-up support, price_jpy, price_usd and price_as_of, plus purchase_url (the checkout confirmation page; the traveler pays there).
| Name | Type | Req | Description |
|---|---|---|---|
| activities | array | – | What the traveler will use mobile data for, when they say so, e.g. ["maps", "social", "video_call"]. hotspot_light / hotspot_heavy mean sharing the connection with another device. Overrides usage. Sa… |
| days | integer | yes | Required. Trip length in days, integer 1 to 180 (the whole trip for a multi-country trip). Example: 7. |
| destination | string | – | One country or region for a single-country trip. Country name in English, Japanese, Chinese, Korean, Spanish or French, common names included (e.g. "Turkey", "Türkiye", "トルコ", "튀르키예", "Hawaii") or an… |
| destinations | array | – | Every country of a multi-country trip (2 to 5 entries; names in any supported language or ISO alpha-2 codes), e.g. ["France", "Italy", "Spain"]. One eSIM that covers all of them is searched. Use inst… |
| lang | string | – | Language of country names, reasons and of the checkout page the link opens: en, ja, zh-cn, zh-tw, ko, es or fr. Default en. The language never changes which plan or what price is returned: every plan… |
| min_gb | number | – | Data the traveler already knows they want, in GB for the whole trip (e.g. 10). Skips the estimate; overrides usage and activities. |
| usage | string | – | Rough data usage when activities are not known: light = maps and messaging, normal = maps, messaging, web and social (default), heavy = normal plus video streaming. Ignored when activities or min_gb… |
| wifi | string | – | How often the traveler will be on hotel or cafe Wi-Fi instead of mobile data: rarely, sometimes (default) or often. More Wi-Fi lowers the estimate. |
No output schema declared.
No examples provided.
search_plans Search plans ~389
Use when the traveler wants to browse or compare Bloomy eSIM plans for one destination themselves. Lists plans cheapest first, single-country plans before regional ones, each with data (GB), validity (days), plan_type, networks (4G/5G), top-up support, price_jpy, price_usd, price_as_of and plan_id. Filter by trip length, minimum GB and plan type. For a recommendation with reasons, recommend_plan is the better fit.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Required. Country name (English, Japanese, Chinese, Korean, Spanish or French) or ISO 3166-1 alpha-2 code, e.g. "Japan", "日本" or "JP". A country with no dedicated plan returns an error, never plans f… |
| lang | string | – | Language of country names, reasons and of the checkout page the link opens: en, ja, zh-cn, zh-tw, ko, es or fr. Default en. The language never changes which plan or what price is returned: every plan… |
| limit | integer | – | Maximum number of plans to return, 1 to 20. Default 8. |
| min_days | integer | – | Trip length in days (integer). Fixed-GB plans valid for fewer days are skipped; daily plans are priced for this many days. |
| min_gb | number | – | Minimum data in GB, e.g. 3. For fixed-GB plans this is the total; for daily plans it is the high-speed allowance per day. |
| plan_type | string | – | "data" = a fixed amount of GB for the whole validity period; "unlimited" = daily plans priced per day (a daily high-speed allowance, then slower speed). Omit to include both. |
No output schema declared.
No examples provided.
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'
What is the Bloomy eSIM MCP server?
Bloomy eSIM is an MCP server listed in the public MCP registry as com.bloomyesim/esim. Travel data eSIMs, 200+ countries: plan picks from destination + days, live prices, 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 85 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 1,922 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 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 Bloomy eSIM MCP server?
VerifyMCP ran 14 checks on Bloomy eSIM, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.