eCommerce

esimker.com

This MCP server facilitates travel destination bookings by providing plans, payment methods, and order management for e-commerce transactions.

1 endpoint12 known toolsFirst detected September 5, 2026Last detected September 5, 2026

ENDPOINT 1

https://esimker.com/api/mcp

No auth detected

MCP server metadata

Name: esimker
Version: 2

Capabilities

experimentalpromptsresourcestools

Server instructions

esimker sells prepaid travel data eSIMs: data only, no phone numbers, no SMS, no voice. Prices are USD strings, from $1.00. No accounts: an order is addressed by a secret token, a wallet by a secret code. Two ways to buy: 1. For a person who pays: search_destinations → get_plans → create_checkout → hand checkout_url to the person → get_order(token) until status is ready. 2. Autonomously from a prepaid wallet: create_wallet once and save its code → send it as `Authorization: Bearer <code>` on every wallet call → create_deposit and pay the address it returns → get_deposit until paid → purchase_esim(plan_id, client_ref) → get_order(token) until ready. Rules: - Confirm the destination, the plan and the price with the person before create_checkout or purchase_esim. An installed eSIM cannot be refunded; a wallet balance is spent on eSIMs and never paid back out. - The wallet code, the order token and the activation code are secrets: keep the code where you keep credentials, show order_url to the buyer only, never log or repeat them elsewhere. A lost wallet code cannot be recovered. - Reuse client_ref when retrying purchase_esim; never create a second checkout while one is open. - daily_unlimited plans are priced per day: pass period_num (1–365, default 7), the amount is price × days. - Regional plans list the countries they cover in location_codes. - A 403 means the caller's jurisdiction is embargoed: tell the person, do not retry.

Known tools 12

search_destinations

Destinations on sale.

Inferred read-only

get_plans

The plans of one destination (slug from search_destinations).

Inferred read-only

get_payment_methods

Checkout methods open right now: "crypto" (a hosted invoice: BTC, ETH, TRX, USDT), "card", and "wallet" (a prepaid balance, see create_wallet).

Potential side effects

create_checkout

Create an order for a person to pay.

Potential side effects

get_order

An order by its token.

Inferred read-only

list_topups

Top-up plans that fit an eSIM we issued: plan_id, name, gb, days, retail.

Inferred read-only

get_usage

Remaining data and status of an eSIM we issued.

Inferred read-only

create_wallet

Mint a prepaid wallet with no account behind it and get its secret ONCE: `code` (32 hex characters) and the same secret as a 12-word `phrase`.

Inferred read-only

get_wallet

The wallet behind the code: ref (a public handle for support), balance_usd, cashback_percent, the deposit rules that apply to it now (min_usd, max_usd, first, bonus tiers), the last 50 transactions, orders (with their tokens — the wallet is where a buyer's order links are kept) and deposits.

Inferred read-only

create_deposit

Open a top-up of the wallet and get what is needed to pay it.

Potential side effects

get_deposit

One deposit of the wallet by its token: status pending → paid (credited, bonus included) | underpaid (nothing credited yet, the rest can still arrive) | expired.

Inferred read-only

purchase_esim

Charge the wallet and issue an eSIM, no checkout.

Potential side effects

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.esimker]
url = "https://esimker.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "esimker": {
      "type": "http",
      "url": "https://esimker.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: esimker
Remote MCP URL: https://esimker.com/api/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": {
    "esimker": {
      "url": "https://esimker.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "esimker": {
      "type": "http",
      "url": "https://esimker.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "esimker",
  "transport": "streamable-http",
  "url": "https://esimker.com/api/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.