MyBestSim MCP server

Which servers in the official MCP registry are MyBestSim's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-17

← Back to MyBestSim

Whose server it is

Registry namecom.mybestsim/esim-comparatorverified in the MCP registry

The registry name sits under mybestsim.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-17

Stateanswerschecked 2026-10-17
Tools4
Server calls itselfmybestsim
Server version1.1.0
Protocol version2025-06-18

On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 545 ms.

Tools it offers4 tools · read 2026-10-17

search_esim_plans
Use this when someone is choosing a travel eSIM or needs mobile data abroad for a given country or region, e.g. "cheapest eSIM for Japan", "10 GB for two weeks in Europe", "unlimited data in the USA". Returns a shortlist (up to 10, at…
plan_trip_esim
Use this when one trip visits SEVERAL countries or regions, e.g. "Japan then China", "two weeks in France, Italy and Spain", "Thailand, Vietnam and Cambodia in March". Pass EVERY stage in travel order, with the days spent in each when…
get_destination_overview
Use this when someone asks how much a travel eSIM costs in a country or region, what the average or typical price is, or how much choice there is, before comparing individual plans. Returns the number of plans and providers listed on the…
get_esim_plan
Use this when someone wants the detail of one plan returned by search_esim_plans or get_destination_overview: coverage (number of countries, region), features, validity and price. Needs the planId and the destination it was found under.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "esim-comparator": {
      "type": "http",
      "url": "https://mcp.mybestsim.com/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.