Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Bloomy eSIM is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Recommend the right travel eSIM for any trip (200+ countries) and hand the traveler a checkout link.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bloomy-esim-mcp https://bloomyesim.com/wp-json/bloomy/v1/mcp
# 2 — ask your agent for something these tools do
# recommend_plan, search_plans, estimate_data and 4 more
Bloomy eSIM costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BLAll 1 server
bloomyesim1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bloomy-esim-mcp https://bloomyesim.com/wp-json/bloomy/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Takes 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. Accepts every country of a multi-country trip in destination
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | no | 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 | no | For a trip through several countries: every country visited (names or ISO codes). One eSIM covering all of them is searched. Alternative to destination. |
| days | integer | yes | Trip length in days (total for a multi-country trip). |
| usage | string | no | light = maps and messaging, normal = maps, messaging, web and social (default), heavy = plus video streaming. Superseded by activities when given. |
| activities | array | no | Specific uses named by the traveler (e.g. hotspot_light for tethering, video_call, video). Overrides usage. Same categories as bloomyesim.com/data-calculator. |
| wifi | string | no | How often hotel/cafe Wi-Fi is used. Default sometimes. |
| min_gb | number | no | Alternative to usage/activities when the GB wanted is already known. |
| lang | string | no | Language for names and for the purchase page. Default en when omitted. The language never changes which plan or what price is returned: every plan carries price_jpy and price_usd (both always present) |
List plans for a destination, cheapest first, single-country plans before multi-country ones. Filter by trip length, minimum GB, and plan type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Required. Country name (any supported language) or ISO alpha-2 code. A country with no dedicated plan returns an error, never plans for a different country. |
| min_days | integer | no | Trip length. Fixed-GB plans shorter than this are skipped; daily plans get the trip total. |
| min_gb | number | no | Minimum GB (daily allowance for daily plans). |
| plan_type | string | no | "data" = fixed GB for the whole period, "unlimited" = priced per day. Omit to include both types. |
| limit | integer | no | Default 8. |
| lang | string | no | Language for names and for the purchase page. Default en when omitted. The language never changes which plan or what price is returned: every plan carries price_jpy and price_usd (both always present) |
Same formula as bloomyesim.com/data-calculator: daily MB per activity x days x Wi-Fi factor x 1.15 safety buffer, rounded up.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | yes | — |
| activities | array | yes | — |
| wifi | string | no | — |
Countries with a dedicated plan, with ISO code, localized name, number of plans and the lowest price. Filterable with query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Part of a country name or code. Omit to list all. |
| lang | string | no | Language for names and for the purchase page. Default en when omitted. The language never changes which plan or what price is returned: every plan carries price_jpy and price_usd (both always present) |
Details of one plan: data, validity, network, 5G, top-up, carriers, price and checkout link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | integer | yes | — |
| days | integer | no | Trip length (sets the day count and total for daily plans). |
| lang | string | no | Language for names and for the purchase page. Default en when omitted. The language never changes which plan or what price is returned: every plan carries price_jpy and price_usd (both always present) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | integer | yes | — |
| days | integer | no | Trip length (needed for daily plans). |
| lang | string | no | Language for names and for the purchase page. Default en when omitted. The language never changes which plan or what price is returned: every plan carries price_jpy and price_usd (both always present) |
Short, accurate setup steps (iPhone or Android), what to check before buying, and links to the full guide, the device checker and troubleshooting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device | string | no | — |
| lang | string | no | Language for names and for the purchase page. Default en when omitted. The language never changes which plan or what price is returned: every plan carries price_jpy and price_usd (both always present) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Bloomy eSIM or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.2.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestda9bb2e3115f075b824e51a6d8a7e9ab390228d9132ea19d195cdb9602d76336
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| recommend_plan | no tags | |
| search_plans | no tags | |
| estimate_data | no tags | |
| list_destinations | no tags | |
| get_plan | no tags | |
| get_purchase_link | no tags | |
| get_setup_guide | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestda9bb2e3115f075b
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Bloomy eSIM can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.