Mono eSIM — Travel Connectivity for AI Agents MCP Server

by andrii-tiurin Your server? Claim it

not responding

Mono eSIM — Travel Connectivity for AI Agents is listed as active in the registry but did not answer our last check. It exposes 21 tools.

Search travel eSIM plans, check devices, and create secure customer-paid checkout links.

Uptime history 7 days of history · worst day 0%

7 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

106 ms

Response time

average over 24h

open, no key

Access

streamable-http

Mono eSIM — Travel Connectivity for AI Agents does not always answer

Over the last week it answered 3.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://www.monoesim.app/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

card

card_payment_terms

Read the currently required consent version and conditions before create_card_authorization. Use this to explain future off-session card charges and spending authority; it never creates a card setup or charges money.

create_card_authorization

Create an offline-sandbox Stripe SetupIntent tied to this authenticated machine after explicit saved-card consent. Call card_payment_terms first, then complete the returned client_secret with Stripe.js and call sync_card_authorization; this call stores consent and limits but does not charge the card. Reuse idempotency_key on retries and never send PAN/CVC to this tool.

revoke

revoke_card_authorization

Revoke an authenticated machine's own saved-card spending permission by authorization_id. This blocks NEW purchases against that permission, but already reserved or in-flight payments may still settle and need reconciliation. This action does not delete the Stripe customer or refund prior charges.

revoke_machine

Permanently disable the authenticated sandbox machine's current API key, preventing subsequent wallet and purchase requests with that key. The transaction and ledger history remain; this does not cash out, refund, or transfer wallet funds. Use only when decommissioning or securing the machine, not when merely changing spending limits.

sync

sync_card_authorization

After completing a Stripe SetupIntent with Stripe.js, reconcile the authenticated machine's saved-card authorization with Stripe. Use the authorization_id returned by create_card_authorization; this may activate the permission only after successful setup and ownership checks, and never charges a card. Do not use it to initiate setup (create_card_authorization) or reconcile an order payment (sync_card_payment).

sync_card_payment

Reconcile a saved-card purchase by the order_id returned from purchase with payment_method=stripe_off_session. For this machine's order, check Stripe PaymentIntent ownership and status; the operation can resume an idempotent pending charge, complete verified fulfilment, or return a required Stripe.js/3-D Secure action. Do not retry with a new order or bypass bank authentication; use get_order to read ordinary delivery status.

wallet

get_wallet

Read the authenticated sandbox machine's own EUR-cent balance, spending limits, and latest ledger entries. Returns at most 100 ledger entries per call; pass offset=100, 200, ... to paginate when next_offset is present. Use fund_wallet to create a test funding checkout and set_wallet_limits to change limits; this read does neither.

set_wallet_limits

Change this authenticated sandbox machine's gross spending limits in integer EUR cents per purchase and per UTC day. Zero blocks future spending; refunds do not restore the consumed daily limit. Use get_wallet to inspect current limits first; this does not authorize another person's card or make a purchase.

checkout

create_checkout

Create a pending customer-paid Stripe Checkout from a quote_id returned by prepare_order, only after the customer explicitly approved the displayed plan and price and accepted the terms. Requires the customer's email and customer_confirmed=true, terms_accepted=true; returns a checkout URL, NOT a paid eSIM, and fulfilment starts only after verified payment. Reuse one idempotency_key per intended purchase, including retries, to avoid duplicate orders; use purchase for other supported payment methods.

compare

compare_plans

Compare 2–10 existing eSIM plan IDs returned by search_plans or get_plan. Returns each matching plan plus the IDs of the cheapest plan, lowest EUR price per GB where calculable, and longest validity; an unknown plan ID is flagged not_found rather than silently replaced. Use for an explicit shortlist, not as the initial destination search; this makes no reservation or purchase.

destinations

list_destinations

List currently offered travel eSIM destinations (countries and multi-country regions) with their localized names, identifiers and starting EUR prices. Use when the travel destination is unknown or to discover valid destinations before search_plans; filter type=country or type=region, or omit it for both. Results are informational only and do not reserve inventory or prices.

device

check_device

Look up a phone model's probable eSIM compatibility by model name (for example 'iPhone 12 mini' or 'Galaxy S21'), using a device list and optional supplier check. Returns supported=true/false/null, close model matches and caveats; null means unknown, not incompatible. Always advise users to confirm an EID and carrier unlock status, especially for regional variants; this is not a purchase approval.

fund

fund_wallet

Create or retrieve an offline-sandbox Stripe TEST Checkout session for funding this authenticated machine's test wallet. amount_cents is integer EUR cents (100 = EUR 1.00); the balance changes only after verified test payment, not after opening the checkout link. Reuse idempotency_key for retries; no real money is accepted.

order

get_order

Retrieve payment/fulfilment status for exactly one order using its order_id AND private order_token returned during checkout or purchase. After confirmed delivery, the response may include activation code (LPA), QR/install links and available usage data; treat the token and activation information as secrets. This is read-only and never confirms payment by itself; do not share the output publicly.

payment

payment_capabilities

Read the payment-method capability matrix BEFORE invoking purchase. Each method reports enabled versus planned status, environment (live/sandbox/offline_sandbox), required customer interaction, supported buyer modes, and any unavailable reason. This is discovery only: listing a planned method does not mean it can charge, and autonomous payments must not fall back silently to human Stripe Checkout.

plan

get_plan

Retrieve one current eSIM plan by plan_id (from search_plans), including EUR price, coverage destination, data allowance, validity, availability, and purchase terms. Use this to confirm an offer before prepare_order; optional destination must be the exact destination slug to narrow lookup, not a free-text city. A missing or withdrawn plan returns not_found; search_plans again instead of relying on cached prices.

plans

search_plans

Find available travel data eSIM plans for a country, city, region, or ISO-2 destination such as 'Japan', 'Tokyo', 'Europe', or 'TR'. Filter by minimum validity (days), minimum data (data_gb), unlimited-only, maximum EUR budget and sort order; returns matching plans, price/validity details and a cheapest-match recommendation, without reserving stock. Use get_plan to validate a selected plan before prepare_order and list_destinations if a location is not recognized.

prepare

prepare_order

Prepare a time-limited signed quote for a plan_id selected using search_plans or get_plan. Returns quote_id, current price and customer-confirmation requirements; the quoted price is locked for 30 minutes, but no order, payment, or eSIM is created. Next call create_checkout for customer-paid Stripe Checkout or purchase for an enabled alternate method.

purchase

purchase

Attempt a purchase for a quote_id from prepare_order using an explicitly selected buyer_mode and payment_method supported by payment_capabilities. stripe_checkout requires human/delegated confirmation, accepted terms, customer email and a customer-paid Stripe link; agent_wallet and stripe_off_session are available only when their offline-sandbox capabilities are enabled and the machine has the necessary authority or balance. This can create an order or start a payment; reuse the SAME idempotency_key on retries and never infer success before verified payment.

register_machine

Create a NEW offline-sandbox machine identity with a zero-EUR test wallet and one-time API key; no email or human account is required. Use before get_wallet, fund_wallet, set_wallet_limits, or sandbox purchases; securely store the returned mak_test_ key, which cannot be retrieved again. This does not create a live payment account.

terms

get_terms

Retrieve the latest displayed eSIM purchase terms and legal links in the requested language (en/de/ru/uk), including delivery, validity, refund/withdrawal conditions and payment. Show these to the customer before confirmation and checkout. This is read-only; it neither records agreement nor grants payment authorization.

Endpoints

URL	Transport	State	Latency	Checked
https://www.monoesim.app/mcp	streamable-http	answering	106 ms	2 min ago

Alternatives to Mono eSIM — Travel Connectivity for AI Agents

same job, measured the same way

Dep

by rog0x

License check, outdated deps, security for AI agents

49 installs/wk local only

Giftroam

by giftroam

Send real gifts to 190+ countries: search, check delivery, get a secure checkout link.

6 tools answering

Arcwall Security

by rom-baro

Security scanning for AI coding tools. Detects secrets, threat models, and runs pre-commit checks.

53 installs/wk local only

The Office Worker

by cafra-house

Local-first document MCP for AI agents: create, read, secure and sign PDF/Word/Excel/PPTX.

137 installs/wk local only

E2b

by mcparmory

Create and manage secure sandboxes for running AI agent code

217 installs/wk local only

Agent Security

by mdfifty50-boop

Security scanning and threat detection for AI agents

60 installs/wk local only

Zn Gate

by usezn

The local security layer for coding agents: secret redaction, injection checks and an MCP proxy.

848 installs/wk local only

Lattice: CVE, MITRE ATT&CK and detection graph for security agents

by namiq

CVE, KEV, MITRE ATT&CK, CWE and detection graph for AI agents; every link names its source.

7 tools answering

Mono eSIM — Travel Connectivity for AI Agents — questions

Answers built from our own checks of this server.

What can Mono eSIM — Travel Connectivity for AI Agents do?

It exposes 21 tools, read directly from the server on our last check. Among them: card_payment_terms, check_device, compare_plans, create_card_authorization, create_checkout, fund_wallet and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Mono eSIM — Travel Connectivity for AI Agents mostly used for?

Its tools cluster around wallet, sync and card. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Mono eSIM — Travel Connectivity for AI Agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 106 ms. The bar chart above shows every period we have measured.

The registry lists Mono eSIM — Travel Connectivity for AI Agents as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Mono eSIM — Travel Connectivity for AI Agents?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Mono eSIM — Travel Connectivity for AI Agents need an API key?

No. Mono eSIM — Travel Connectivity for AI Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.