_ registry / mcp streamable-http · checked 47m ago

bloomy-esim

https://bloomyesim.com

Registry code: 34fbdd70461de849

api record

Bloomy eSIM sells data-only travel eSIMs (no phone number, no SMS) for 200+ countries and regions. Start with recommend_plan (destination + days, plus how they use data if known). Show the options with price and reason, then give the traveler the purchase_url of the one they pick. The traveler pays on that page; this server never takes payment. The QR code is emailed and shown in My Page right after payment. Validity starts when the eSIM first connects at the destination, so they can buy and install before departure. Use get_setup_guide for installation questions. If the traveler pastes an…

endpoint
https://bloomyesim.com/wp-json/bloomy/v1/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is bloomy-esim live?
Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
Is bloomy-esim free to use?
Yes — the hub reached it with no key and no payment.
What tools does bloomy-esim have?
7 tools: get_setup_guide, get_purchase_link, get_plan, recommend_plan, search_plans, estimate_data, list_destinations.
Is bloomy-esim safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
775ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 309 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • find a travel esim for a destination
  • estimate mobile data needs for a trip
  • get an esim purchase link
  • get esim setup steps
takes → gives
text, data → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
2 open 5 never probed 2 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • estimate_data reads open 8h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "days",
    "activities"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 180,
      "minimum": 1
    },
    "wifi": {
      "enum": [
        "rarely",
        "sometimes",
        "often"
      ],
      "type": "string"
    },
    "activities": {
      "type": "array",
      "items": {
        "enum": [
          "maps",
          "messaging",
          "web",
          "music",
          "voice",
          "social",
          "video_call",
          "hotspot_light",
          "video",
          "hotspot_heavy"
        ],
        "type": "string"
      }
    }
  }
}
    arguments 40 lines
  • list_destinations reads open 47m ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ja",
        "zh-cn",
        "zh-tw",
        "ko",
        "es",
        "fr"
      ],
      "type": "string",
      "description": "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)."
    },
    "query": {
      "type": "string",
      "description": "Part of a country name or code. Omit to list all."
    }
  }
}
    arguments 22 lines
  • get_setup_guide reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ja",
        "zh-cn",
        "zh-tw",
        "ko",
        "es",
        "fr"
      ],
      "type": "string",
      "description": "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)."
    },
    "device": {
      "enum": [
        "iphone",
        "android"
      ],
      "type": "string"
    }
  }
}
    arguments 25 lines
  • get_purchase_link reads unknown 8h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "plan_id"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "description": "Trip length (needed for daily plans)."
    },
    "lang": {
      "enum": [
        "en",
        "ja",
        "zh-cn",
        "zh-tw",
        "ko",
        "es",
        "fr"
      ],
      "type": "string",
      "description": "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)."
    },
    "plan_id": {
      "type": "integer"
    }
  }
}
    arguments 28 lines
  • get_plan reads unknown 8h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "plan_id"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "description": "Trip length (sets the day count and total for daily plans)."
    },
    "lang": {
      "enum": [
        "en",
        "ja",
        "zh-cn",
        "zh-tw",
        "ko",
        "es",
        "fr"
      ],
      "type": "string",
      "description": "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)."
    },
    "plan_id": {
      "type": "integer"
    }
  }
}
    arguments 28 lines
  • recommend_plan reads unknown 47m ago

    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 destinations, with the total days.

    mcp-tool

    {
  "type": "object",
  "required": [
    "days"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 180,
      "minimum": 1,
      "description": "Trip length in days (total for a multi-country trip)."
    },
    "lang": {
      "enum": [
        "en",
        "ja",
        "zh-cn",
        "zh-tw",
        "ko",
        "es",
        "fr"
      ],
      "type": "string",
      "description": "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)."
    },
    "wifi": {
      "enum": [
        "rarely",
        "sometimes",
        "often"
      ],
      "type": "string",
      "description": "How often hotel/cafe Wi-Fi is used. Default sometimes."
    },
    "usage": {
      "enum": [
        "light",
        "normal",
        "heavy"
      ],
      "type": "string",
      "description": "light = maps and messaging, normal = maps, messaging, web and social (default), heavy = plus video streaming. Superseded by activities when given."
    },
    "min_gb": {
      "type": "number",
      "description": "Alternative to usage/activities when the GB wanted is already known."
    },
    "activities": {
      "type": "array",
      "items": {
        "enum": [
          "maps",
          "messaging",
          "web",
          "music",
          "voice",
          "social",
          "video_call",
          "hotspot_light",
          "video",
          "hotspot_heavy"
        ],
        "type": "string"
      },
      "description": "Specific uses named by the traveler (e.g. hotspot_light for tethering, video_call, video). Overrides usage. Same categories as bloomyesim.com/data-calculator."
    },
    "destination": {
      "type": "string",
      "description": "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": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "description": "For a trip through several countries: every country visited (names or ISO codes). One eSIM covering all of them is searched. Alternative to destination."
    }
  }
}
    arguments 80 lines
  • search_plans reads unknown 47m ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "destination"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ja",
        "zh-cn",
        "zh-tw",
        "ko",
        "es",
        "fr"
      ],
      "type": "string",
      "description": "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)."
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Default 8."
    },
    "min_gb": {
      "type": "number",
      "description": "Minimum GB (daily allowance for daily plans)."
    },
    "min_days": {
      "type": "integer",
      "description": "Trip length. Fixed-GB plans shorter than this are skipped; daily plans get the trip total."
    },
    "plan_type": {
      "enum": [
        "data",
        "unlimited"
      ],
      "type": "string",
      "description": "\"data\" = fixed GB for the whole period, \"unlimited\" = priced per day. Omit to include both types."
    },
    "destination": {
      "type": "string",
      "description": "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."
    }
  }
}
    arguments 47 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 34fbdd70461de849.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/34fbdd70461de849/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/34fbdd70461de849/badge.svg)](https://brick.blue/agent/34fbdd70461de849?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.