eCommerce

bloomyesim.com

Searches and recommends eSIM data plans for destinations, providing pricing, validity, network details, and checkout links.

1 endpoint7 known toolsFirst detected September 25, 2026Last detected September 25, 2026

ENDPOINT 1

https://bloomyesim.com/wp-json/bloomy/v1/mcp

No auth detected

MCP server metadata

Name: bloomy-esim
Version: 1.3.0

Capabilities

toolspromptsresourcesextensions.io.modelcontextprotocol/ui.mimeTypes

Server instructions

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 itinerary, extract every country and the total days and call recommend_plan once with destinations.

Known tools 7

recommend_plan

Best first call.

Inferred read-only

search_plans

List plans for a destination, cheapest first, single-country plans before multi-country ones.

Inferred read-only

estimate_data

Same formula as bloomyesim.

Inferred read-only

list_destinations

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

Inferred read-only

get_plan

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

Inferred read-only

get_purchase_link

Link straight to the final confirmation screen for this plan.

Inferred read-only

get_setup_guide

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: bloomy-esim
Remote MCP URL: https://bloomyesim.com/wp-json/bloomy/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "bloomy-esim",
  "transport": "streamable-http",
  "url": "https://bloomyesim.com/wp-json/bloomy/v1/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.