varioroam MCP server

• Registry namecom.varioroam/esim-catalogverified in the MCP registry

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

• Stateanswerschecked 2026-10-28
• Tools8
• Server calls itselfvarioroam
• Server version1.2.4
• Protocol version2025-06-18

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

• Its tools do buy a data pool sized to a country and trip length, but not share the trip data with a laptop via hotspot; connect a travel router to an eSIM for group data.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score79 of 100answers 100 · does the job 33 · definitions 88 · context 100 · connects 100
• What an agent can do with it1 of 3 use cases
• Answered100% of days7 of 7 daily checks
• Median first answer816 ms
• Space in an agent's context≈ 2,919 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsB · 88 of 100
• Typed results2 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_shop_facts

  What varioroam is and how it works, in the shop’s own words: the configurable eSIM, ranges, delivery, payment, hotspot, activation, top-ups (add data or days), e-mails, support. Use for any question that is not a price.

• list_destinations

  Every country varioroam can build an eSIM for, with the number of selectable networks and the starting price (1 GB, 1 day, cheapest network). Use to check coverage or to compare many countries at once.

• get_networks

  The mobile networks the customer can tick for one country (operator name, 4G/5G) with the price of a reference eSIM on each network alone (1 GB · 7 days), so you can say which network is the cheapest and what the others add.

• quote_esim

  Use while the customer is still deciding — "how much is …?": the exact price of one eSIM configuration (country, data GB 1–100, days 1–90, networks), the server price the customer would pay. Quote it as returned, never compute or scale it…

• price_grid

  Prices for several GB × days combinations of one country in one call (max 8 × 8), e.g. to compare with other providers or to find the best fit for a trip. Same server prices as quote_esim.

• recommend_config

  Use when the customer describes a trip instead of a size: country (or up to 5), days and how they use data (usage light / normal / heavy, or gb_per_day). Sizes the data pool from the data guide and returns three server-quoted…

• plan_trip

  A trip through several countries (max 5): one eSIM per country, each quoted with the same data pool and days unless given per country (gb omitted = sized for normal use from the days). Returns one line per country with price and buy_url…

• start_checkout

  Use only once the customer has decided to buy ("I'll take it", "how do I buy?"): the checkout handoff. Returns the buy_url to give the customer, the final price and a ready-to-send checkout block (next_step, payment_methods, delivery)…