MonoEsim

About

MonoEsim connects an assistant to a travel eSIM shop. It can list destinations, search and compare data plans, check phone eSIM compatibility, read purchase terms, prepare a price quote, create a Stripe Checkout link and track order delivery. Sandbox tools cover machine wallets and saved-card authorizations for autonomous purchases.

The hosted endpoint runs over streamable HTTP. No sign-in or API key is needed for searching and quoting. Sandbox wallet and card tools use a machine API key returned by register_machine. Human purchases are paid by the customer through a Stripe Checkout link, after explicit consent to the terms.

What you can do

• List eSIM destinations by country or region
• Search plans by days, data, budget and unlimited
• Compare 2 to 10 plans by price, price per GB and validity
• Check phone eSIM compatibility
• Prepare a locked 30 minute price quote
• Create a customer-paid Stripe Checkout link
• Track order and delivery status
• Manage sandbox wallets and saved-card permissions

Tools 26

• search_plansRead-only

  Find eSIM plans for a destination with filters for days, data, budget and sort.

• list_destinationsRead-only

  List offered countries and regions with starting EUR prices.

• get_planRead-only

  Get current details for one plan by plan_id.

• compare_plansRead-only

  Compare 2 to 10 plans by price, price per GB and validity.

• check_deviceRead-only

  Look up a phone model's probable eSIM compatibility.

• get_termsRead-only

  Get purchase terms and legal links in en, de, ru or uk.

• prepare_orderRead-only

  Create a signed quote that locks the price for 30 minutes.

• create_checkoutWrites

  Create a customer-paid Stripe Checkout link from a quote.

• get_orderRead-only

  Get payment and delivery status using order_id and order_token.

• payment_capabilitiesRead-only

  List payment methods with enabled or planned status and requirements.

• purchaseWrites

  Start a purchase from a quote using a chosen buyer mode and payment method.

• card_payment_termsRead-only

  Read the consent version and conditions for saved-card authorization.

Read from the live server on 12 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

• Find a 10 GB eSIM for 10 days in Japan under 15 EUR

• Compare these two eSIM plans for my trip to Italy

• Will my iPhone 12 mini work with an eSIM?

• Show the purchase terms for the eSIM in English

Set up

Every client connects to monoesim.app. Pick yours; the page remembers your choice.

claude mcp add --transport http monoesim https://www.monoesim.app/mcp

https://www.monoesim.app/mcp

{
  "mcpServers": {
    "monoesim": {
      "url": "https://www.monoesim.app/mcp"
    }
  }
}

code --add-mcp '{"name":"monoesim","type":"http","url":"https://www.monoesim.app/mcp"}'

{
  "servers": {
    "monoesim": {
      "type": "http",
      "url": "https://www.monoesim.app/mcp"
    }
  }
}

{
  "mcpServers": {
    "monoesim": {
      "serverUrl": "https://www.monoesim.app/mcp"
    }
  }
}

codex mcp add monoesim --url https://www.monoesim.app/mcp

[mcp_servers.monoesim]
url = "https://www.monoesim.app/mcp"

gemini mcp add --transport http monoesim https://www.monoesim.app/mcp

{
  "mcpServers": {
    "monoesim": {
      "type": "http",
      "url": "https://www.monoesim.app/mcp"
    }
  }
}

Embed

Show MonoEsim in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge Website card iframe JSON AI prompt

README badge

Markdown

[![MonoEsim on mcp.tc](https://mcp.tc/i/monoesim/badge.svg)](https://mcp.tc/i/monoesim)

HTML

<a href="https://mcp.tc/i/monoesim"><img src="https://mcp.tc/i/monoesim/badge.svg" alt="MonoEsim on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML

<script src="https://mcp.tc/w/monoesim.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML

<iframe src="https://mcp.tc/embed/monoesim" title="MonoEsim on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/monoesim.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the MonoEsim card to your site.

Markdown

Add the mcp.tc card for MonoEsim, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/monoesim.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="monoesim"><a href="https://mcp.tc/i/monoesim">MonoEsim on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![MonoEsim on mcp.tc](https://mcp.tc/i/monoesim/badge.svg)](https://mcp.tc/i/monoesim)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 12 Nov 2026, 05:48 UTC.

1. 11 Nov 2026, 02:45 UTC, Automatic check

   New version 1.5.0 (was 1.4.0). Reported by the server.

2. 11 Nov 2026, 02:45 UTC, Automatic check

   5 tools added and 8 tools changed. Server instructions changed.

   New server instructions

   Details, 11 Nov 2026, 02:45 UTC

   Added 5

   • get_affiliateRead-only

     Read your affiliate account with your API key: state (awaiting_owner_confirmation, active, pending_review, blocked), referral link and ?ref= code, QR image, clicks and sales, balance in EUR (available, on hold, processing, paid), and whether your owner completed the payout setup. Read-only; customer data is never included.

   • get_referral_linkRead-only

     Build your tracked link (requires an active affiliate key): pass plan_id for a plan page with the plan preselected, destination (country, city, region or ISO-2) for a destination page, or nothing for your partner landing page. Share only where advertising is allowed and mark it as an ad; the price returned is current and may change.

   • list_affiliate_salesRead-only

     List sales made through your referral link (latest first, 50 per page): date, destination, plan, amount, refunds, your commission and its state (held, available, settled, void). Contains no customer data. Requires an active affiliate key.

   • register_affiliateWrites

     Register this AI agent as a MonoEsim affiliate (call WITHOUT an API key). Pass the email of the human who owns you, your name, where and how you will promote MonoEsim, and accept_program_rules=true after reading the rules. Returns a one-time API key at once; the owner must confirm by email before referral links and commission work. Payouts go only to payout details the owner saves in the partner portal.

   • request_payoutWrites

     Ask MonoEsim to pay out your available commission (requires an active affiliate key, available balance at or above the minimum and the owner's completed payout setup). Creates at most one open request; MonoEsim then issues a credit note and transfers the money to the payout details the owner saved. You can never set or change payout details.

   Changed 8

   • compare_plansinput schema
   • create_checkoutinput schema
   • get_planinput schema
   • get_termsinput schema
   • list_destinationsinput schema
   • prepare_orderinput schema
   • purchaseinput schema
   • search_plansinput schema

   Server instructions

   Before

   MonoEsim (https://www.monoesim.app) sells prepaid travel data eSIMs for countries and regional packs. Prices are final consumer prices in EUR, read live from the catalog. Find and compare: search_plans(destination, days, data_gb) -> recommend 1-3 plans -> compare_plans for a shortlist -> check_device when unsure whether the phone supports eSIM -> get_plan for the current price and details -> get_terms to show the conditions. list_destinations lists every destination. Buy with checkout: prepare_order(plan_id) -> show plan, price and terms, get the customer's explicit yes and email -> create_checkout(quote_id, email, customer_confirmed=true, terms_accepted=true, idempotency_key) -> give the customer checkout_url; the customer pays on Stripe themselves -> get_order(order_id, order_token) until status=delivered -> help install. Alternatively give the customer the plan's `url` (official destination page with ?plan=<plan_id> preselected) and let them buy there. Rules: quote only prices returned by the tools (they change); never confirm anything on the customer's behalf; keep API keys and order tokens private. The wallet and saved-card tools belong to an offline sandbox that is not enabled here; payment_capabilities shows what is enabled.

   After

   MonoEsim (https://www.monoesim.app) sells prepaid travel data eSIMs for countries and regional packs. Prices are final consumer prices in EUR, read live from the catalog. Find and compare: search_plans(destination, days, data_gb) -> recommend 1-3 plans -> compare_plans for a shortlist -> check_device when unsure whether the phone supports eSIM -> get_plan for the current price and details -> get_terms to show the conditions. list_destinations lists every destination. Buy with checkout: prepare_order(plan_id) -> show plan, price and terms, get the customer's explicit yes and email -> create_checkout(quote_id, email, customer_confirmed=true, terms_accepted=true, idempotency_key) -> give the customer checkout_url; the customer pays on Stripe themselves -> get_order(order_id, order_token) until status=delivered -> help install. Alternatively give the customer the plan's `url` (official destination page with ?plan=<plan_id> preselected) and let them buy there. Rules: quote only prices returned by the tools (they change); never confirm anything on the customer's behalf; keep API keys and order tokens private. Affiliate programme: an agent can earn commission for its human owner. register_affiliate(owner_email, agent_name, promotion_plan, accept_program_rules=true) without an API key -> the owner confirms by email -> with the returned key: get_affiliate (status, referral link, balance), get_referral_link(destination or plan_id), list_affiliate_sales, request_payout. Promote only where ads are allowed, mark ads as ads, never spam; payouts go only to the details the owner saves in the partner portal. The wallet and saved-card tools belong to an offline sandbox that is not enabled here; payment_capabilities shows what is enabled.

3. 9 Nov 2026, 14:49 UTC, Automatic check

   8 tools changed.

   Details, 9 Nov 2026, 14:49 UTC

   Changed 8

   • compare_plansinput schema
   • create_checkoutinput schema
   • get_planinput schema
   • get_termsinput schema
   • list_destinationsinput schema
   • prepare_orderinput schema
   • purchaseinput schema
   • search_plansinput schema

4. 9 Nov 2026, 05:43 UTC, Automatic check

   8 tools changed.

   Details, 9 Nov 2026, 05:43 UTC

   Changed 8

   • compare_plansinput schema
   • create_checkoutinput schema
   • get_planinput schema
   • get_termsinput schema
   • list_destinationsinput schema
   • prepare_orderinput schema
   • purchaseinput schema
   • search_plansinput schema

5. 8 Nov 2026, 17:54 UTC, Automatic check

   Server instructions changed.

   New server instructions

   Details, 8 Nov 2026, 17:54 UTC

   Server instructions

   Before

   MonoEsim (https://www.monoesim.app) sells prepaid travel data eSIMs for countries and regional packs. Prices are final consumer prices in EUR, read live from the catalog. Find and compare: search_plans(destination, days, data_gb) -> recommend 1-3 plans -> compare_plans for a shortlist -> check_device when unsure whether the phone supports eSIM -> get_plan for the current price and details -> get_terms to show the conditions. list_destinations lists every destination. Buying: agent checkout is not enabled at the moment, so create_checkout and purchase(stripe_checkout) refuse with checkout_unavailable. To buy, give the customer the plan's `url` — the official destination page with ?plan=<plan_id> preselected. The customer checks the price, enters their email and pays on the website themselves; the eSIM arrives by email and on the order page. Never say an order was placed or paid. Rules: quote only prices returned by the tools (they change); never confirm anything on the customer's behalf; keep API keys and order tokens private. The wallet and saved-card tools belong to an offline sandbox that is not enabled here; payment_capabilities shows what is enabled.

   After

   MonoEsim (https://www.monoesim.app) sells prepaid travel data eSIMs for countries and regional packs. Prices are final consumer prices in EUR, read live from the catalog. Find and compare: search_plans(destination, days, data_gb) -> recommend 1-3 plans -> compare_plans for a shortlist -> check_device when unsure whether the phone supports eSIM -> get_plan for the current price and details -> get_terms to show the conditions. list_destinations lists every destination. Buy with checkout: prepare_order(plan_id) -> show plan, price and terms, get the customer's explicit yes and email -> create_checkout(quote_id, email, customer_confirmed=true, terms_accepted=true, idempotency_key) -> give the customer checkout_url; the customer pays on Stripe themselves -> get_order(order_id, order_token) until status=delivered -> help install. Alternatively give the customer the plan's `url` (official destination page with ?plan=<plan_id> preselected) and let them buy there. Rules: quote only prices returned by the tools (they change); never confirm anything on the customer's behalf; keep API keys and order tokens private. The wallet and saved-card tools belong to an offline sandbox that is not enabled here; payment_capabilities shows what is enabled.

6. 8 Nov 2026, 14:48 UTC, Automatic check

   New version 1.4.0 (was 1.3.0). Reported by the server.

7. 8 Nov 2026, 14:48 UTC, Automatic check

   Server instructions changed.

   New server instructions

   Details, 8 Nov 2026, 14:48 UTC

   Server instructions

   Before

   First call payment_capabilities to discover available payment methods. purchase is the universal entry point. Planned adapters are unavailable; never claim a payment succeeded without verified order status. Autonomous modes do not require human consent per purchase, but require an enabled autonomous adapter and authorized funds. MonoEsim sells travel data eSIMs (190+ countries, regional packs), prices in EUR. Typical flow: search_plans(destination, days, data_gb) -> recommend 1-3 plans -> check_device if unsure -> prepare_order(plan_id) -> show price + terms, get explicit customer consent and email -> create_checkout(quote_id, email, customer_confirmed=true, terms_accepted=true, idempotency_key) -> give the customer checkout_url to pay -> get_order(order_id, order_token) until status=delivered -> help install. For human Stripe Checkout, obtain explicit customer consent before setting customer_confirmed or terms_accepted. For an enabled agent_wallet sandbox: register_machine -> fund_wallet -> purchase(payment_method=agent_wallet, buyer_mode=autonomous_agent, terms_accepted=true). The machine may accept terms within its existing authority and spend its own funded balance without human confirmation or email. For enabled stripe_off_session sandbox, first obtain prior payment authority and complete create_card_authorization/SetupIntent. Then purchase with authorization_id and no per-purchase human confirmation. If requires_action is returned, the payer must complete Stripe authentication before delivery; use sync_card_payment to reconcile. Never invent payment authority or prices. Keep API keys and order_token private.

   After

   MonoEsim (https://www.monoesim.app) sells prepaid travel data eSIMs for countries and regional packs. Prices are final consumer prices in EUR, read live from the catalog. Find and compare: search_plans(destination, days, data_gb) -> recommend 1-3 plans -> compare_plans for a shortlist -> check_device when unsure whether the phone supports eSIM -> get_plan for the current price and details -> get_terms to show the conditions. list_destinations lists every destination. Buying: agent checkout is not enabled at the moment, so create_checkout and purchase(stripe_checkout) refuse with checkout_unavailable. To buy, give the customer the plan's `url` — the official destination page with ?plan=<plan_id> preselected. The customer checks the price, enters their email and pays on the website themselves; the eSIM arrives by email and on the order page. Never say an order was placed or paid. Rules: quote only prices returned by the tools (they change); never confirm anything on the customer's behalf; keep API keys and order tokens private. The wallet and saved-card tools belong to an offline sandbox that is not enabled here; payment_capabilities shows what is enabled.

8. 2 Nov 2026, 20:30 UTC, Automatic check

   Tracking started: 21 tools.

FAQ